From: Eli Zaretskii <eliz@gnu.org>
To: Chris Genly <chgenly@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: gdb.texinfo patch for -var-list-children
Date: Thu, 18 Jun 2009 14:42:00 -0000 [thread overview]
Message-ID: <E1MHIol-0006uX-QT@fencepost.gnu.org> (raw)
In-Reply-To: <ed4903890906171348o70235199t8668323171f2dc65@mail.gmail.com> (message from Chris Genly on Wed, 17 Jun 2009 13:48:21 -0700)
> Date: Wed, 17 Jun 2009 13:48:21 -0700
> From: Chris Genly <chgenly@gmail.com>
>
> The gdb documentation for the MI command -var-list-children does not
> match what Eclipse DSF expects, nor what Cygwin gcc generates. This
> patch corrects the documentation.
Thanks, this patch is approved. But please format the ChangeLog entry
according to our standards: it should mention the file name and the
node name where you make the changes. See gdb/doc/ChangeLog for
examples.
Do you have write access to the GDB repository? If you do, please
commit the changes after you fix the log entry. If not, I will commit
this when I get back from traveling (if no one else beats me to it).
Thanks again for working on this.
next prev parent reply other threads:[~2009-06-18 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 20:48 Chris Genly
2009-06-18 14:42 ` Eli Zaretskii [this message]
2009-06-20 4:12 ` Chris Genly
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=E1MHIol-0006uX-QT@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=chgenly@gmail.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