From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: [remote] RFC: Replace qPart with qXfer
Date: Sat, 24 Jun 2006 02:24:00 -0000 [thread overview]
Message-ID: <20060623215242.GA5944@nevyn.them.org> (raw)
In-Reply-To: <uejxfagrd.fsf@gnu.org>
On Fri, Jun 23, 2006 at 09:06:30PM +0300, Eli Zaretskii wrote:
> In the case in point, I think that "*Note FOO, and *Note BAR" sounds
> better than with the extra "see". You don't have the "in" in your
> sentence, so the situation is different from what the manual
> describes. In the printed version, removing "see" will produce this:
>
> See Section X.YZ [OS Information], page 123, and Section A.BC
> [read-aux-vector], page 456.
>
> which is okay, I think.
Gotcha. Thanks.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-23 21:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-22 8:42 Daniel Jacobowitz
2006-06-22 9:05 ` Vladimir Prus
2006-06-22 12:35 ` What's the difference between gdb arm targets? Dave Murphy
2006-06-22 12:39 ` Daniel Jacobowitz
2006-06-22 13:17 ` [remote] RFC: Replace qPart with qXfer Daniel Jacobowitz
2006-06-23 16:23 ` Eli Zaretskii
2006-06-23 18:06 ` Daniel Jacobowitz
2006-06-23 20:10 ` Eli Zaretskii
2006-06-24 2:24 ` Daniel Jacobowitz [this message]
2006-06-25 3:10 ` Karl Berry
2006-06-25 4:07 ` Eli Zaretskii
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=20060623215242.GA5944@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
/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