From: "Tom Browder" <tom.browder@gmail.com>
To: "Ben Elliston" <bje@au1.ibm.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, doc]: Fix typo.
Date: Tue, 01 Apr 2008 10:47:00 -0000 [thread overview]
Message-ID: <8bc817ee0804010346k5fcd16d5sf8d75b18a3019625@mail.gmail.com> (raw)
In-Reply-To: <1207027909.8147.1.camel@localhost>
On Tue, Apr 1, 2008 at 12:31 AM, Ben Elliston <bje@au1.ibm.com> wrote:
> I'm committing the following as obvious. I'm reasonably certain to have
> got the intended meaning correct here, but if I haven't, please let me
> know. In the meantime, I don't think this patch will make things
> worse. :-)
Ben, could I get your support for this attempted patch for the same
file? Joseph is very busy, but this is one the order of yours.
http://gcc.gnu.org/ml/gcc-patches/2008-02/msg00102.html
Thanks.
-Tom
Tom Browder
Niceville, Florida
USA
next prev parent reply other threads:[~2008-04-01 10:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-01 5:34 Ben Elliston
2008-04-01 10:47 ` Tom Browder [this message]
2008-04-02 2:47 ` Ben Elliston
2008-04-06 18:54 ` Gerald Pfeifer
2008-04-07 11:49 ` Tom Browder
2020-04-01 17:19 [PATCH] doc: " Segher Boessenkool
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=8bc817ee0804010346k5fcd16d5sf8d75b18a3019625@mail.gmail.com \
--to=tom.browder@gmail.com \
--cc=bje@au1.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
/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).