From: Gerald Pfeifer <gerald@pfeifer.com>
To: Ian Lance Taylor <iant@google.com>
Cc: alfred.minarik@aon.at, gcc-patches@gcc.gnu.org,
Tom Tromey <tromey@redhat.com>
Subject: Re: [C++ PATCH] PR13676 resubmission: Detect additional file extensions as C++ headers
Date: Fri, 27 Jul 2007 22:34:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.0707280025070.19878@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <m3sl793n1e.fsf@localhost.localdomain>
On Fri, 27 Jul 2007, Ian Lance Taylor wrote:
> This patch:
>
> http://gcc.gnu.org/ml/gcc-patches/2007-02/msg00331.html
>
> is OK for mainline.
I believe Alfred does not have SVN write access.
Alfred, if you send me a patch tested against current SVN, I will be
happy to apply it for you.
Gerald
next prev parent reply other threads:[~2007-07-27 22:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-27 15:56 Ian Lance Taylor
2007-07-27 22:34 ` Gerald Pfeifer [this message]
2007-07-29 5:47 ` AW: " Alfred Minarik
2007-08-06 11:11 ` Gerald Pfeifer
-- strict thread matches above, loose matches on Subject: below --
2007-02-04 17:22 Alfred Minarik
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=Pine.LNX.4.64.0707280025070.19878@acrux.dbai.tuwien.ac.at \
--to=gerald@pfeifer.com \
--cc=alfred.minarik@aon.at \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=tromey@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).