From: Diego Novillo <dnovillo@google.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: reply@codereview.appspotmail.com, lxo@redhat.com,
crowl@google.com, gchare@google.com,
gcc-patches@gcc.gnu.org
Subject: Re: [pph contrib] Add support for multiple spawn patterns in repro_fail (issue4571061)
Date: Fri, 24 Jun 2011 13:30:00 -0000 [thread overview]
Message-ID: <BANLkTinUKan2eY0Y35ueSPtTCy3w-xno8g@mail.gmail.com> (raw)
In-Reply-To: <oroc1r2fqv.fsf@livre.localdomain>
On Tue, Jun 21, 2011 at 14:36, Alexandre Oliva <aoliva@redhat.com> wrote:
> On Jun 10, 2011, dnovillo@google.com (Diego Novillo) wrote:
>
>> I'm thinking that this script is better written in python, but that
>> may make it less generic and I don't know whether we accept python in
>> gcc/contrib. Alex?
>
> I guess anything goes in gcc/contrib, so it could be rewritten in
> Python, but the bash script you checked in looks good enough to me.
Thanks. I committed the script to trunk r175374.
Diego.
prev parent reply other threads:[~2011-06-24 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 23:52 Diego Novillo
2011-06-21 18:50 ` Alexandre Oliva
2011-06-24 13:30 ` Diego Novillo [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=BANLkTinUKan2eY0Y35ueSPtTCy3w-xno8g@mail.gmail.com \
--to=dnovillo@google.com \
--cc=aoliva@redhat.com \
--cc=crowl@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gchare@google.com \
--cc=lxo@redhat.com \
--cc=reply@codereview.appspotmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).