From: Stan Shebs <stanshebs@earthlink.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "Maciej W. Rozycki" <macro@codesourcery.com>,
tromey@redhat.com, justin.lebar@gmail.com,
gdb-patches@sourceware.org
Subject: Re: Status of 'blacklist' patch?
Date: Thu, 03 Nov 2011 19:01:00 -0000 [thread overview]
Message-ID: <4EB2E4E7.1020408@earthlink.net> (raw)
In-Reply-To: <8362j1m5bw.fsf@gnu.org>
On 11/3/11 11:25 AM, Eli Zaretskii wrote:
>> Date: Thu, 3 Nov 2011 18:04:08 +0000
>> From: "Maciej W. Rozycki"<macro@codesourcery.com>
>> CC: Eli Zaretskii<eliz@gnu.org>,<justin.lebar@gmail.com>,
>> <stanshebs@earthlink.net>,<gdb-patches@sourceware.org>
>>
>> What about the other places where @subsection is used without @node --
>> are they legitimate?
> They are legitimate, but having sections and subsections without a
> @node makes finding them harder, since there's no commands in Info to
> find a section by name, only by its node name. So I'd like to avoid
> introducing more of them.
>
That's a good deal my fault - at one point I had it stuck in my head
that makeinfo could auto-generate nodes from section headings, but in
reviewing the texinfo doc, it looks like
I must have confused that with auto-generation of next/prev/up links (or
else it was an option
that came and went long ago).
Stan
stan@codesourcery.com
next prev parent reply other threads:[~2011-11-03 19:01 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 12:12 Diego Novillo
2011-10-06 14:08 ` Justin Lebar
2011-10-06 15:51 ` Stan Shebs
2011-10-06 20:16 ` Justin Lebar
2011-10-10 12:34 ` Stan Shebs
2011-10-11 21:34 ` Justin Lebar
2011-10-11 23:54 ` Doug Evans
2011-10-16 19:22 ` Justin Lebar
2011-10-20 19:46 ` Tom Tromey
2011-10-25 20:07 ` Justin Lebar
2011-10-25 20:41 ` Pedro Alves
2011-10-25 21:25 ` Justin Lebar
2011-10-20 20:40 ` Eli Zaretskii
2011-10-25 16:47 ` Justin Lebar
2011-10-25 16:53 ` Eli Zaretskii
2011-10-25 19:52 ` Justin Lebar
2011-10-25 20:13 ` Eli Zaretskii
2011-10-25 20:30 ` Justin Lebar
2011-10-26 1:06 ` Stan Shebs
2011-10-26 3:45 ` Justin Lebar
2011-10-26 5:37 ` Stan Shebs
2011-10-26 8:10 ` Joel Brobecker
2011-10-26 13:28 ` Eli Zaretskii
2011-10-26 15:11 ` Justin Lebar
2011-10-28 18:18 ` Tom Tromey
2011-10-28 19:48 ` Justin Lebar
2011-10-28 19:53 ` Tom Tromey
2011-10-28 19:49 ` Tom Tromey
2011-10-28 19:55 ` Justin Lebar
2011-10-28 20:37 ` Tom Tromey
2011-10-31 15:52 ` Justin Lebar
[not found] ` <4EAF2E0E.7080508@earthlink.net>
2011-11-01 14:53 ` Justin Lebar
2011-11-02 22:43 ` Maciej W. Rozycki
2011-11-02 23:52 ` Stan Shebs
2011-11-03 0:20 ` Maciej W. Rozycki
2011-11-03 3:54 ` Eli Zaretskii
2011-11-03 14:32 ` Tom Tromey
2011-11-03 16:54 ` Eli Zaretskii
2011-11-03 18:04 ` Maciej W. Rozycki
2011-11-03 18:25 ` Eli Zaretskii
2011-11-03 19:01 ` Stan Shebs [this message]
2011-10-06 17:19 ` Diego Novillo
2011-10-06 17:33 ` Tom Tromey
2011-10-06 17:37 ` Diego Novillo
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=4EB2E4E7.1020408@earthlink.net \
--to=stanshebs@earthlink.net \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=justin.lebar@gmail.com \
--cc=macro@codesourcery.com \
--cc=tromey@redhat.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