From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: [remote] RFC: Replace qPart with qXfer
Date: Fri, 23 Jun 2006 18:06:00 -0000 [thread overview]
Message-ID: <20060623171419.GA28992@nevyn.them.org> (raw)
In-Reply-To: <u8xnparul.fsf@gnu.org>
On Thu, Jun 22, 2006 at 10:54:42PM +0300, Eli Zaretskii wrote:
> > Date: Wed, 21 Jun 2006 23:17:31 -0400
> > From: Daniel Jacobowitz <drow@false.org>
> >
> > Does anyone have any comments on this proposed change?
>
> I saw some irregularities and tried to guess what was wrong in the
> Texinfo sources; hopefully this will be useful.
Thanks!
> > Access the target's "auxiliary vector". *Note auxiliary
> > vector: OS Information, and see *Note read-aux-vector-packet:
> ^^^
> This "see" is redundant. I suspect you used "see @ref"; if so, just
> drop the "see" part.
(This was just moved from the qPart description.)
Confused. The example in the Texinfo manual suggests "see @ref", and
says that you shouldn't just drop it, because e.g. "in *Note" is
considered awkward.
http://www.gnu.org/software/texinfo/manual/texinfo/html_node/ref.html#index-ref-374
> > `m DATA'
> > Data DATA (*note Binary Data:: has been read from the target.
> ^^^
> A missing right paren after @pxref.
>
> > `l DATA'
> > Data DATA (*note Binary Data:: has been read from the target.
>
> Same here.
Right on both counts. Fixed, thank you much.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-06-23 17:14 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 [this message]
2006-06-23 20:10 ` Eli Zaretskii
2006-06-24 2:24 ` Daniel Jacobowitz
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=20060623171419.GA28992@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