From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: Phil Edwards <phil@jaj.com>, Benjamin Kosnik <bkoz@redhat.com>
Cc: gcc@gcc.gnu.org, Joe Buck <jbuck@synopsys.com>,
Matthias Klose <doko@cs.tu-berlin.de>
Subject: Re: draft release notes for gcc 3.3
Date: Thu, 08 May 2003 07:14:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.55.0305080912110.23217@acrux.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20030507171315.4d4209ed.bkoz@redhat.com>
On Wed, 7 May 2003, Phil Edwards wrote:
> I'd vote for omitting it if possible, e.g., PR12345.
On Wed, 7 May 2003, Benjamin Kosnik wrote:
> Ditto.
Both http://gcc.gnu.org/PR?666
and http://gcc.gnu.org/PR666
should work now.
Let's see what Joe thinks, but perhaps just using the latter is
preferrable, as it doesn't contain a shell meta character, so, for
example, copy&paste into "lynx ..." works fine, without adding quotes?
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.pfeifer.com/gerald/
next prev parent reply other threads:[~2003-05-08 7:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-07 22:14 Benjamin Kosnik
2003-05-07 22:46 ` Joe Buck
2003-05-08 7:14 ` Gerald Pfeifer [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-07 17:50 Benjamin Kosnik
2003-05-07 18:06 ` Joe Buck
2003-05-07 21:30 ` Benjamin Kosnik
2003-05-07 21:43 ` Phil Edwards
2003-05-08 23:59 ` Joe Buck
2003-05-09 2:59 ` Benjamin Kosnik
2003-05-09 4:28 ` Benjamin Kosnik
2003-05-09 16:20 ` Joe Buck
2003-05-09 16:34 ` Benjamin Kosnik
2003-05-09 7:24 ` Matthias Klose
2003-05-09 16:24 ` Benjamin Kosnik
2003-05-07 17:28 Joe Buck
2003-05-07 18:04 ` Phil Edwards
2003-05-07 21:35 ` Gerald Pfeifer
2003-05-07 21:42 ` Steven Bosscher
2003-05-07 21:45 ` Phil Edwards
2003-05-07 22:17 ` Joe Buck
2003-05-08 9:46 ` Gabriel Dos Reis
2003-05-07 18:45 ` Steven Bosscher
2003-05-07 19:32 ` Joe Buck
2003-05-08 2:10 ` Kaveh R. Ghazi
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=Pine.BSF.4.55.0305080912110.23217@acrux.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=bkoz@redhat.com \
--cc=doko@cs.tu-berlin.de \
--cc=gcc@gcc.gnu.org \
--cc=jbuck@synopsys.com \
--cc=phil@jaj.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).