Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Doug Evans <dje@google.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Merge dg-extract-results.{sh,py} from GCC upstream
Date: Tue, 16 Dec 2014 00:39:00 -0000	[thread overview]
Message-ID: <87d27k5syd.fsf@redhat.com> (raw)
In-Reply-To: <CADPb22SPJ8DhdGOjZPZz=Mw3y+CSxGHKo5aLdKDqRf4H0y9YmA@mail.gmail.com>	(Doug Evans's message of "Mon, 15 Dec 2014 16:29:18 -0800")

On Monday, December 15 2014, Doug Evans wrote:

> On Mon, Dec 15, 2014 at 3:33 PM, Sergio Durigan Junior
> <sergiodj@redhat.com> wrote:
>> It has been a while since we don't sync this file with GCC upstream,
>> and in the meantime some interesting things have happened.  The most
>> interesting is the inclusion of a new dg-extract-results.py which is
>> apparently faster than its shell equivalent.
[...]
> Ok by me.

Thanks, pushed.

  <https://sourceware.org/ml/gdb-cvs/2014-12/msg00074.html>
  395cf596db32c02f34fa211cf49c3e9231d7c277

-- 
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


  reply	other threads:[~2014-12-16  0:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-15 23:33 Sergio Durigan Junior
2014-12-16  0:29 ` Doug Evans
2014-12-16  0:39   ` Sergio Durigan Junior [this message]
2015-02-12 20:27 ` Pedro Alves
2015-02-12 20:32   ` Sergio Durigan Junior
2015-02-12 20:38     ` Pedro Alves
2015-02-12 20:47       ` Sergio Durigan Junior
2015-03-09 17:50     ` Merge 'Make dg-extract-results.sh explicitly treat .{sum,log}, files as text' change (Re: [PATCH] Merge dg-extract-results.{sh,py} from GCC upstream) Pedro Alves
2015-03-09 17:53     ` [pushed] Delete gdb/testsuite/dg-extract-results.py " Pedro Alves

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=87d27k5syd.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=dje@google.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