From: Nathanael Nerode <neroden@twcny.rr.com>
To: gcc@gcc.gnu.org
Subject: Re: Old bug: the 14-character limit.
Date: Fri, 23 May 2003 19:44:00 -0000 [thread overview]
Message-ID: <20030523194244.GA13382@doctormoo> (raw)
That should read bug 4293. *cough*.
next reply other threads:[~2003-05-23 19:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 19:44 Nathanael Nerode [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-23 19:41 Nathanael Nerode
2003-05-23 19:52 ` DJ Delorie
2003-05-25 18:17 ` Andris Pavenis
2003-05-23 20:44 ` Laurent GUERBY
2003-05-23 20:45 ` Neil Booth
2003-05-23 20:53 ` Phil Edwards
2003-05-23 20:53 ` Mike Stump
2003-05-23 20:54 ` DJ Delorie
2003-05-23 21:34 ` Laurent GUERBY
2003-05-23 21:53 ` DJ Delorie
2003-05-24 9:27 ` Laurent GUERBY
2003-05-24 14:23 ` DJ Delorie
2003-05-24 2:19 ` Michael S. Zick
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=20030523194244.GA13382@doctormoo \
--to=neroden@twcny.rr.com \
--cc=gcc@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).