From: Jeff Law <law@redhat.com>
To: Anthony Brandon <anthony.brandon@gmail.com>, pinskia@gmail.com
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
"manu@gcc.gnu.org" <manu@gcc.gnu.org>,
"joseph@codesourcery.com" <joseph@codesourcery.com>
Subject: Re: [PATCH] cleanup in c-parser
Date: Mon, 13 Oct 2014 18:54:00 -0000 [thread overview]
Message-ID: <543C1F7E.9080001@redhat.com> (raw)
In-Reply-To: <CALsyMRgUCb2Zwmz+KLRyRF-Q8yHnYtPThxzdjwjr6scXOzUAxg@mail.gmail.com>
On 10/13/14 05:11, Anthony Brandon wrote:
> I updated the patch with a comment. Actually, Manuel handed me this
> patch just to help me get familiar with the process of submitting and
> testing.
> Generating this one with git diff looks different so I'm not sure if
> that's a problem or not.
This version is fine. Please install on the trunk.
Thanks,
jeff
next prev parent reply other threads:[~2014-10-13 18:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-12 19:41 Anthony Brandon
2014-10-12 20:36 ` pinskia
2014-10-13 11:21 ` Anthony Brandon
2014-10-13 18:54 ` Jeff Law [this message]
2014-10-13 21:05 ` Manuel López-Ibáñez
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=543C1F7E.9080001@redhat.com \
--to=law@redhat.com \
--cc=anthony.brandon@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=manu@gcc.gnu.org \
--cc=pinskia@gmail.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).