public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: mike stump <mrs@windriver.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: preprocessor/6021: \^M handling wrong when not followed by ^J
Date: Mon, 25 Mar 2002 16:16:00 -0000 [thread overview]
Message-ID: <20020326001602.25014.qmail@sources.redhat.com> (raw)
The following reply was made to PR preprocessor/6021; it has been noted by GNATS.
From: mike stump <mrs@windriver.com>
To: gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
neil@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: preprocessor/6021: \^M handling wrong when not followed by ^J
Date: Mon, 25 Mar 2002 16:08:21 -0800 (PST)
Doh! Mac! Ick! I forgot about that... If the files really expose
themselves as foo\rbar... then I guess this isn't a bug. Sorry about
that.
> Date: 24 Mar 2002 21:04:26 -0000
> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, mrs@mail.wrs.com,
> nobody@gcc.gnu.org
> From: neil@gcc.gnu.org
> Synopsis: \^M handling wrong when not followed by ^J
> State-Changed-From-To: open->feedback
> State-Changed-By: neil
> State-Changed-When: Sun Mar 24 13:04:25 2002
> State-Changed-Why:
> Hi Mike,
>
> Would you elaborate a bit on this issue? We handle '\r' as a newline since that is what is it on a Mac.
>
> What's an ASR 33?
> http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6021
next reply other threads:[~2002-03-26 0:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-25 16:16 mike stump [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-25 23:06 neil
2002-03-24 13:04 neil
2002-03-20 19:56 mrs
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=20020326001602.25014.qmail@sources.redhat.com \
--to=mrs@windriver.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).