From: Diego Novillo <dnovillo@google.com>
To: Lawrence Crowl <crowl@google.com>
Cc: reply@codereview.appspotmail.com,
Gabriel Charette <gchare@google.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [pph] New script to reproduce failures from a .log file (issue4601050)
Date: Thu, 09 Jun 2011 22:08:00 -0000 [thread overview]
Message-ID: <BANLkTikZjTBU-HiBrNo5C1x=1c45No5RSw@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=X648H==7pQSSYTVfTvnx3R9kA5w@mail.gmail.com>
On Thu, Jun 9, 2011 at 13:48, Lawrence Crowl <crowl@google.com> wrote:
>
> line=$(sed -e "/^spawn .*$pattern/ ! d ; s/^spawn //" $logf)
>
> Has one fewer process and one fewer pipe. Sed is your friend.
sed and I have a complicated relationship. But, sure :)
> I think this code fails when multiple lines match the pattern.
> Pipe through head?
Yup. It does.
I'm sure there will be other things, it's in contrib/ now. I'll wait
until we've used it and expanded it a bit more and move it to trunk.
Diego.
next prev parent reply other threads:[~2011-06-09 21:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 18:40 Diego Novillo
2011-06-09 21:27 ` Lawrence Crowl
2011-06-09 22:08 ` Diego Novillo [this message]
2011-06-10 6:36 ` Alexandre Oliva
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='BANLkTikZjTBU-HiBrNo5C1x=1c45No5RSw@mail.gmail.com' \
--to=dnovillo@google.com \
--cc=crowl@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gchare@google.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).