From: Diego Novillo <dnovillo@google.com>
To: Tom de Vries <Tom_deVries@mentor.com>
Cc: Yury Gribov <y.gribov@samsung.com>,
tbsaunde@tbsaunde.org, GCC Patches <gcc-patches@gcc.gnu.org>,
Jeff Law <law@redhat.com>
Subject: Re: [PATCH][PING^2] Skip preprocessor directives in mklog
Date: Tue, 12 May 2015 16:13:00 -0000 [thread overview]
Message-ID: <CAD_=9DSMqN1VeBQxizSjY-QPKAYsaYYcHevT1FnOhfT7sE8c6A@mail.gmail.com> (raw)
In-Reply-To: <5552215A.6010005@mentor.com>
On Tue, May 12, 2015 at 11:50 AM, Tom de Vries <Tom_deVries@mentor.com> wrote:
> I'm not a good choice to be the maintainer of a perl script.
I'm all kinds of sorry about the original choice of scripting
language. I'd just spend a couple of hours re-writing it in python.
next prev parent reply other threads:[~2015-05-12 16:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 11:26 [PATCH] " Yury Gribov
2015-04-21 12:32 ` Tom de Vries
2015-04-30 9:23 ` [PATCH][PING] " Yury Gribov
2015-05-12 15:23 ` [PATCH][PING^2] " Yury Gribov
2015-05-12 15:23 ` Diego Novillo
2015-05-12 15:33 ` Yury Gribov
2015-05-12 15:58 ` Tom de Vries
2015-05-12 16:13 ` Diego Novillo [this message]
2015-05-12 16:01 ` Trevor Saunders
2015-05-12 16:24 ` Yury Gribov
2015-05-12 19:59 ` Jeff Law
2015-05-12 20:29 ` Jeff Law
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='CAD_=9DSMqN1VeBQxizSjY-QPKAYsaYYcHevT1FnOhfT7sE8c6A@mail.gmail.com' \
--to=dnovillo@google.com \
--cc=Tom_deVries@mentor.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=tbsaunde@tbsaunde.org \
--cc=y.gribov@samsung.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).