From: Eli Zaretskii <eliz@gnu.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: drow@false.org, gdb-patches@sources.redhat.com
Subject: Re: [RFA] -list-target-groups --available
Date: Mon, 01 Dec 2008 20:39:00 -0000 [thread overview]
Message-ID: <uej0rljho.fsf@gnu.org> (raw)
In-Reply-To: <200812011111.21264.vladimir@codesourcery.com>
> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Mon, 1 Dec 2008 11:11:20 +0300
> Cc: drow@false.org, gdb-patches@sources.redhat.com
>
> > . @appendix is an equivalent of @section, so its immediate sub-nodes
> > cannot be @section's. They should be @appendixsubsec instead.
>
> That lead to texinfo/tex errors. @appendixsection, however, appears to
> work fine both to info and pdf output.
Sorry, my bad. Yes, @appendixsection is the right command.
> > > +Each item is required to include a column with name of @samp{pid},
> > > +that identifies the process.
> >
> > "name of `pid'" does not sound right. Do you mean " the name of the
> > process identified by @var{pid}"?
>
> I mean that:
>
> - the name of the column should be 'pid'
> - the value of the column should identify the process
>
> I've clarified this and also addressed Dan's comments. Revised patch
> attached, OK?
Yes, but I have a better suggestion:
> +Each item should include a column with name of @samp{pid}.
Each item should include a column whose name is @samp{pid}.
next prev parent reply other threads:[~2008-12-01 20:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-14 18:55 Vladimir Prus
2008-11-21 0:46 ` Daniel Jacobowitz
2008-11-23 2:14 ` Vladimir Prus
2008-11-23 5:16 ` Vladimir Prus
2008-11-24 22:11 ` Daniel Jacobowitz
2008-11-23 16:11 ` Pedro Alves
2008-11-24 23:13 ` Eli Zaretskii
2008-11-25 2:41 ` Eli Zaretskii
2008-12-01 8:12 ` Vladimir Prus
2008-12-01 20:39 ` Eli Zaretskii [this message]
2008-11-25 6:13 ` 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=uej0rljho.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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