From: Eli Zaretskii <eliz@gnu.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH: doco] gdbint.texinfo
Date: Mon, 25 Jun 2007 10:32:00 -0000 [thread overview]
Message-ID: <utzswohm4.fsf@gnu.org> (raw)
In-Reply-To: <18046.59452.336943.780543@kahikatea.snap.net.nz> (message from Nick Roberts on Mon, 25 Jun 2007 09:55:08 +1200)
> From: Nick Roberts <nickrob@snap.net.nz>
> Date: Mon, 25 Jun 2007 09:55:08 +1200
> Cc: gdb-patches@sources.redhat.com
>
> 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?
That's close, but I'd like to shorten some more:
> + * Initializing a New Architecture::
Initialize New Architecture
> + * Pointers Are Not Always Addresses::
Pointers and Addresses
> + * Raw and Virtual Register Representations::
Raw and Virtual Registers
> + * Register and Memory Data Representations::
Register and Memory Data
Thanks.
next prev parent reply other threads:[~2007-06-25 3:09 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
2007-06-25 10:32 ` Eli Zaretskii [this message]
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=utzswohm4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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