Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: naesten@gmail.com, gdb-patches@sourceware.org, tromey@redhat.com,
	dje@google.com
Subject: Re: [PATCH v4] Resurrect gdb-add-index as a contrib script
Date: Fri, 15 Nov 2013 16:38:00 -0000	[thread overview]
Message-ID: <837gc9ipun.fsf@gnu.org> (raw)
In-Reply-To: <20131115145421.GA3096@host2.jankratochvil.net>

> Date: Fri, 15 Nov 2013 15:54:21 +0100
> From: Jan Kratochvil <jan.kratochvil@redhat.com>
> Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>,
>         Doug Evans <dje@google.com>, Eli Zaretskii <eliz@gnu.org>
> 
> On Sun, 03 Nov 2013 22:57:59 +0100, Samuel Bronson wrote:
> > --- a/gdb/NEWS
> > +++ b/gdb/NEWS
> > @@ -32,6 +32,9 @@
> >    Before, the former would print "<optimized out>", and the latter
> >    "*value not available*".
> >  
> > +* New script contrib/gdb-add-index.sh for adding .gdb_index sections
> > +  to binaries.
> > +
> >  * Python scripting
> >  
> >    ** Frame filters and frame decorators have been added.
> 
> Eli usually reviews the NEWS part.

Oops, sorry for missing that.  This part is OK.

Thanks.


  reply	other threads:[~2013-11-15 16:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-03 22:52 [PATCH] " Samuel Bronson
2013-11-04  2:05 ` Samuel Bronson
2013-11-04 21:17   ` Samuel Bronson
2013-11-07 20:10 ` Jan Kratochvil
2013-11-07 21:54   ` Tom Tromey
2013-11-09  6:23 ` [PATCH v2] " Samuel Bronson
2013-11-09 18:41 ` [PATCH v3] " Samuel Bronson
2013-11-11 19:46   ` Doug Evans
2013-11-15  3:31 ` [PATCH v4] " Samuel Bronson
2013-11-15 10:50   ` Doug Evans
2013-11-15 15:27   ` Jan Kratochvil
2013-11-15 16:38     ` Eli Zaretskii [this message]
2013-11-15 22:00 ` [PATCH v5] " Samuel Bronson
2013-11-16 12:12   ` Jan Kratochvil

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=837gc9ipun.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=naesten@gmail.com \
    --cc=tromey@redhat.com \
    /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