From: "Ollie Wild" <aaw@google.com>
To: "Mark Mitchell" <mark@codesourcery.com>
Cc: "Ian Lance Taylor" <iant@google.com>,
gnu@the-meissners.org, wilson@specifixinc.com,
tromey@redhat.com, gcc-patches@gcc.gnu.org
Subject: Re: PATCH PING: distcc and ccache speedup: adds directives-only preprocessing
Date: Mon, 30 Jul 2007 18:53:00 -0000 [thread overview]
Message-ID: <65dd6fd50707301134m44f235ffvb364fdda7e2914c@mail.gmail.com> (raw)
In-Reply-To: <46ACE2AD.9060507@codesourcery.com>
On 7/29/07, Mark Mitchell <mark@codesourcery.com> wrote:
> The patch is OK with those changes.
Thanks, Mark. I've updated the documentation per your suggestions and
committed the change.
Ollie
next prev parent reply other threads:[~2007-07-30 18:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 16:10 Ian Lance Taylor
2007-07-25 16:27 ` Andreas Schwab
2007-07-26 7:16 ` Mark Mitchell
2007-07-26 10:51 ` Dave Korn
2007-07-26 19:37 ` Ian Lance Taylor
2007-07-26 22:10 ` Ollie Wild
2007-07-29 19:29 ` Mark Mitchell
2007-07-30 18:53 ` Ollie Wild [this message]
2007-07-27 23:17 ` Michael Meissner
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=65dd6fd50707301134m44f235ffvb364fdda7e2914c@mail.gmail.com \
--to=aaw@google.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gnu@the-meissners.org \
--cc=iant@google.com \
--cc=mark@codesourcery.com \
--cc=tromey@redhat.com \
--cc=wilson@specifixinc.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).