From: Doug Evans <dje@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [doc RFA] "set debug dwarf2-read" and "set debug symtab-create"
Date: Tue, 26 Jun 2012 20:16:00 -0000 [thread overview]
Message-ID: <CADPb22RQJeqN2XLLtq+V1-facBh2oPBqaj2NCTGDTCA_jcAc_Q@mail.gmail.com> (raw)
In-Reply-To: <83zk7q82fr.fsf@gnu.org>
On Tue, Jun 26, 2012 at 9:26 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Date: Tue, 26 Jun 2012 08:45:04 -0700
> > From: Doug Evans <dje@google.com>
> > Cc: gdb-patches <gdb-patches@sourceware.org>
> >
> > Hi. "Ping." :-)
>
> Sorry, but your wording was ambiguous:
>
> > > I'm committing this after a doc RFA.
>
> I interpreted that as meaning "doc review was already done, I'm
> committing this".
>
> > --- a/gdb/NEWS
> > +++ b/gdb/NEWS
> > @@ -462,6 +462,16 @@ tstop [NOTES]
> >
> > * New options
> >
> > +set debug dwarf2-read
> > +show debug dwarf2-read
> > + Turns on or off display of GDB info related to reading DWARF debugging
> > + information. The default is off.
>
> I'd prefer to say "display of debugging messages related to reading
> DWARF debug info".
>
> > +@item set debug dwarf2-read
> > +@cindex DWARF2 Reading
> > +Turns on or off display of @value{GDBN} info related to reading
> > +DWARF debugging information. The default is off.
> > +@item show debug dwarf2-read
> > +Show the current state of DWARF2 reader debugging.
>
> Same here.
>
> > +@item set debug symtab-create
> > +@cindex Symbol Table Creation
>
> Index entries should start with a lower-case letter. I would simply
> lower-case all the words in this entry.
>
> OK with those changes.
>
>
> Thanks, and sorry for the delay.
Committed with the suggested changes.
Thanks, and no worries.
prev parent reply other threads:[~2012-06-26 20:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 22:27 Doug Evans
2012-06-22 14:06 ` Tom Tromey
2012-06-23 22:58 ` Doug Evans
2012-06-26 15:45 ` Doug Evans
2012-06-26 16:26 ` Eli Zaretskii
2012-06-26 20:16 ` Doug Evans [this message]
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=CADPb22RQJeqN2XLLtq+V1-facBh2oPBqaj2NCTGDTCA_jcAc_Q@mail.gmail.com \
--to=dje@google.com \
--cc=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