Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Hope <michael.hope@linaro.org>
Cc: brobecker@adacore.com, joseph@codesourcery.com,
	gdb-patches@sourceware.org
Subject: Re: [PATCH, doc]: Rename Index node to prevent file collision
Date: Thu, 21 Jun 2012 16:22:00 -0000	[thread overview]
Message-ID: <83ipekd496.fsf@gnu.org> (raw)
In-Reply-To: <CANLjY-mxLOu3+0ohZc-=N7vCDg2se-gGFzc5w8nUzZoWQ1M8oA@mail.gmail.com>

> From: Michael Hope <michael.hope@linaro.org>
> Date: Thu, 21 Jun 2012 16:19:48 +1200
> Cc: brobecker@adacore.com, joseph@codesourcery.com, gdb-patches@sourceware.org
> 
> > I fail to understand why working around by changes in one file
> > (gdb.texinfo) is acceptable, but working around in another file
> > (makeinfo's source) is not.  I guess I'm missing something.
> 
> GDB is an active project.  Even if makeinfo was alive, it's nice to be
> able to use the tools already shipped with long term releases like
> Ubuntu 10.04.

Texinfo is actively maintained as well.  It is also nice to be able to
generate a manual without having to jump through hoops.

It simply sounds unfair that you are asking a project to fix problems
of another.

> > The problem with your suggestion is that the GDB index is not a
> > concept index, it is all the indices lumped into one.  But I would be
> > OK if we separate the concept index from the rest, and then we could
> > have "Concept Index" and "Command and Variable Index".
> 
> I'd rather not go there as it's a big change for little gain.

??? It's as simple as modifying the "@syncodeindex" directives at the
beginning of gdb.texinfo, and then adding 2 @node lines for the two
indices, instead of the current one.  All the rest will be done by
makeinfo.  Am I missing something?


  reply	other threads:[~2012-06-21 16:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-14  2:39 Michael Hope
2012-06-14 15:06 ` Joseph S. Myers
2012-06-14 16:42   ` Eli Zaretskii
2012-06-14 21:43     ` Michael Hope
2012-06-14 22:01       ` Joel Brobecker
2012-06-14 22:27         ` Michael Hope
2012-06-15  7:44           ` Eli Zaretskii
2012-06-15  7:36         ` Eli Zaretskii
2012-06-15 12:19           ` Joel Brobecker
2012-06-17 23:26           ` Michael Hope
2012-06-18  2:53             ` Eli Zaretskii
2012-06-21  4:20               ` Michael Hope
2012-06-21 16:22                 ` Eli Zaretskii [this message]
2012-06-21 22:36                   ` Michael Hope
2012-06-22  5:58                     ` Eli Zaretskii
2012-06-22 10:03                       ` Eli Zaretskii
2012-07-01 19:56                         ` Eli Zaretskii
2012-07-02  1:03                           ` Michael Hope
2012-07-03 16:23                             ` Eli Zaretskii
2012-07-11  5:14                             ` Terry Guo
     [not found]                             ` <000201cd5f24$1ff8e8c0$5feaba40$%guo@arm.com>
2012-07-12  7:57                               ` Eli Zaretskii
2012-06-15  7:29       ` Eli Zaretskii
2012-06-17 23:18         ` Michael Hope

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=83ipekd496.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=joseph@codesourcery.com \
    --cc=michael.hope@linaro.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