From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Make dg-extract-results.sh explicitly treat .{sum,log} files as text
Date: Mon, 15 Dec 2014 22:15:00 -0000 [thread overview]
Message-ID: <20141215221522.GA27989@host2.jankratochvil.net> (raw)
In-Reply-To: <87vblc5zyi.fsf@redhat.com>
On Mon, 15 Dec 2014 23:07:49 +0100, Sergio Durigan Junior wrote:
> Is there any documented procedure to merge this file later?
git log gdb/testsuite/dg-extract-results.sh
shows some commits like:
Merge dg-extract-results.sh from gcc upstream (svn 195224).
or
* dg-extract-results.sh: Sync with GCC HEAD (import r155655, r157175
and r157645).
> Ops, OK, thanks, I will submit the patch to gcc-patches then.
+
> BTW, I see that the Python version already takes care of binary logs.
Does the patch to gcc-patches make sense then?
Jan
next prev parent reply other threads:[~2014-12-15 22:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 21:00 Sergio Durigan Junior
2014-12-15 21:33 ` Jan Kratochvil
2014-12-15 22:07 ` Sergio Durigan Junior
2014-12-15 22:15 ` Jan Kratochvil [this message]
2014-12-15 22:17 ` Sergio Durigan Junior
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=20141215221522.GA27989@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@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