From: Eli Zaretskii <eliz@gnu.org>
To: gdb-patches@sourceware.org
Subject: Re: [RFC, take 2] Optional expat
Date: Tue, 08 Aug 2006 19:16:00 -0000 [thread overview]
Message-ID: <uhd0ndomk.fsf@gnu.org> (raw)
In-Reply-To: <20060808180706.GC24779@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 8 Aug 2006 14:07:06 -0400)
> Date: Tue, 8 Aug 2006 14:07:06 -0400
> From: Daniel Jacobowitz <drow@false.org>
>
> +@node Requirements
> +@section Requirements for building @value{GDBN}
I think this section would benefit from at least one @cindex entry.
> +use the @samp{--with-libexpat-prefix} option to specify its location.
I think @option is better than @samp here.
> +@cindex configuring @value{GDBN}
> +@cindex configuring @value{GDBN}, and source tree subdirectories
Please remove the second @cindex entry. (Yes, I know you just moved
it from the current place.) It's a bad idea to have several index
entries that begin with the same (long) string and point to the same
page.
Other than that, the doco patch is okay with me.
next prev parent reply other threads:[~2006-08-08 19:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-08 18:07 Daniel Jacobowitz
2006-08-08 19:16 ` Eli Zaretskii [this message]
2006-08-08 19:28 ` Daniel Jacobowitz
2006-08-08 21:32 ` Eli Zaretskii
2006-08-08 20:22 ` Mark Kettenis
2006-08-08 20:27 ` 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=uhd0ndomk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@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