Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Chris Genly <chgenly@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: gdb.texinfo patch for -var-list-children
Date: Sat, 20 Jun 2009 04:12:00 -0000	[thread overview]
Message-ID: <ed4903890906192112j7c684909o1da33a887cdca4f4@mail.gmail.com> (raw)
In-Reply-To: <E1MHIol-0006uX-QT@fencepost.gnu.org>

I don't have change access to the gdb sources.  Sorry about the
ChangeLog format.

On Thu, Jun 18, 2009 at 7:42 AM, Eli Zaretskii<eliz@gnu.org> wrote:
> 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.


      reply	other threads:[~2009-06-20  4:12 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
2009-06-20  4:12   ` Chris Genly [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=ed4903890906192112j7c684909o1da33a887cdca4f4@mail.gmail.com \
    --to=chgenly@gmail.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