Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/Doco] Document new <data-dir>/system-gdbinit area
Date: Wed, 22 May 2013 14:54:00 -0000	[thread overview]
Message-ID: <83obc3t68n.fsf@gnu.org> (raw)
In-Reply-To: <20130522062815.GZ4017@adacore.com>

> Date: Wed, 22 May 2013 10:28:15 +0400
> From: Joel Brobecker <brobecker@adacore.com>
> Cc: gdb-patches@sourceware.org
> 
> > Ugh, a subsection without a @node...  Why people like them so much?
> > They make navigation inside an Info reader harder.
> 
> I didn't know... I will gladly fix it.

Thanks.

> First attached is a patch which provides the changes made on top
> of the first submission, showing the changes I made based on your
> feedback. It also includes a NEWS entry.
> 
> And second patch is the actual full patch.
> 
> gdb/doc/ChangeLog:
> 
>         * gdb.texinfo (Installed System-wide Configuration Scripts):
>         Add subsection describing the scripts now available under
>         the data-dir's system-gdbbinit subdirectory.
>         * NEWS: Add entry announcing the availability of system-wide
>         configuration scripts for ElinOS and Wind River Linux.
> 
> OK to commit?

Yes, with one gotcha:

> +@node Installed System-wide Configuration Scripts
> +@subsection Installed System-wide Configuration Scripts
> +@cindex System-wide configuration scripts

@cindex entries should begin with a lower-case letter, unless it's a
proper name or acronym.  (This is because mixed-case sorts differently
in different locales.)

Thanks.


  reply	other threads:[~2013-05-22 14:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-21  9:25 Joel Brobecker
2013-05-21 15:34 ` Pedro Alves
2013-05-21 17:37   ` Eli Zaretskii
2013-05-21 17:17 ` Eli Zaretskii
2013-05-22  6:28   ` Joel Brobecker
2013-05-22 14:54     ` Eli Zaretskii [this message]
2013-05-23  6:08       ` Checked in: " Joel Brobecker
2013-05-24  1:33         ` asmwarrior
2013-05-24  4:53           ` Joel Brobecker
2013-05-24  5:06             ` Joel Brobecker
2013-05-24  6:24             ` Eli Zaretskii
2013-05-22  6:44   ` Joel Brobecker

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=83obc3t68n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=brobecker@adacore.com \
    --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