From: Mike Stump <mrs@apple.com>
To: Rask Ingemann Lambertsen <rask@sygehus.dk>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Improve fatal_expected_char() EOF reporting
Date: Thu, 30 Nov 2006 22:53:00 -0000 [thread overview]
Message-ID: <0AE077FC-9C31-467C-BB37-7B055C8E7499@apple.com> (raw)
In-Reply-To: <20061130194302.GE3563@sygehus.dk>
On Nov 30, 2006, at 11:43 AM, Rask Ingemann Lambertsen wrote:
> On Tue, Nov 28, 2006 at 02:20:11PM -0800, Mike Stump wrote:
>> On Nov 28, 2006, at 12:43 PM, Rask Ingemann Lambertsen wrote:
>>> This patches changes fatal_expected_char() to print "EOF" instead.
>>
>> Looks good to me. Looks trivial and obvious as well.
>
> I don't have write access. Please commit it for me. Thanks.
I've used up my all my spare I think this is obvious coins for the
year. :-(
next prev parent reply other threads:[~2006-11-30 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-28 20:52 Rask Ingemann Lambertsen
2006-11-28 22:28 ` Mike Stump
2006-11-30 20:07 ` Rask Ingemann Lambertsen
2006-11-30 22:53 ` Mike Stump [this message]
2007-08-10 8:52 ` PING " Rask Ingemann Lambertsen
2007-08-24 0:44 ` Ian Lance Taylor
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=0AE077FC-9C31-467C-BB37-7B055C8E7499@apple.com \
--to=mrs@apple.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rask@sygehus.dk \
/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).