From: Nick Roberts <nickrob@snap.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH: doco] gdbint.texinfo
Date: Mon, 25 Jun 2007 00:36:00 -0000 [thread overview]
Message-ID: <18046.59452.336943.780543@kahikatea.snap.net.nz> (raw)
In-Reply-To: <uy7i9nqmq.fsf@gnu.org>
Eli Zaretskii writes:
> > From: Nick Roberts <nickrob@snap.net.nz>
> > Date: Sun, 24 Jun 2007 18:32:31 +1200
> >
> >
> > I still get confused by target and architecture (sometimes, they seem to be
> > used interchangeably) but how about adding a menu and creating nodes as below?
>
> It's okay, but please make the long node names shorter. Long node
> names look badly in an Info reader
I'm reluctant to make my own names as I only have a shallow understanding.
How about if I use the cindex names as node names?
+ @menu
+ * OS ABI Variant Handling::
+ * Initializing a New Architecture::
+ * Registers and Memory::
+ * Pointers Are Not Always Addresses::
+ * Address Classes::
+ * Raw and Virtual Register Representations::
+ * Register and Memory Data Representations::
+ * Frame Interpretation::
+ * Inferior Call Setup::
+ * Compiler Characteristics::
+ * Target Conditionals::
+ * Adding a New Target::
+ * Converting Targets to Multi-arch::
+ @end menu
That's shorter but I don't know if it's short enough.
--
Nick http://www.inet.net.nz/~nickrob
next prev parent reply other threads:[~2007-06-24 21:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-24 6:32 Nick Roberts
2007-06-24 18:40 ` Eli Zaretskii
2007-06-25 0:36 ` Nick Roberts [this message]
2007-06-25 10:32 ` Eli Zaretskii
2007-06-24 19:13 ` Daniel Jacobowitz
2007-06-24 21:42 ` Daniel Jacobowitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18046.59452.336943.780543@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox