From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: Mark Mitchell <mark@codesourcery.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: GCC 3.0.2 Release
Date: Thu, 25 Oct 2001 13:09:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.33.0110252104430.31494-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <57510000.1004034201@gandalf.codesourcery.com>
On Thu, 25 Oct 2001, Mark Mitchell wrote:
> Although the GNU mirror sites have the tarballs at this point, the GCC
> mirror sites do not, due to an error on my part. I have uploaded the
> tarballs now, and they will reach the GCC mirrors shortly.
What about the diffs (which aren't yet on gcc.gnu.org)?
> Joseph Meyers
Please learn to spell my name correctly in release announcements.
> The GCC 3.0 branch is now unfrozen.
What is the target date for 3.0.3?
--
Joseph S. Myers
jsm28@cam.ac.uk
next prev parent reply other threads:[~2001-10-25 13:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-25 11:25 Mark Mitchell
2001-10-25 13:09 ` Joseph S. Myers [this message]
2001-12-01 5:02 ` Joe Comunale
-- strict thread matches above, loose matches on Subject: below --
2001-10-23 10:09 GCC 3.0.2 release Mark Mitchell
2001-10-23 11:00 ` Joseph S. Myers
2001-10-23 11:14 ` Mark Mitchell
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.LNX.4.33.0110252104430.31494-100000@kern.srcf.societies.cam.ac.uk \
--to=jsm28@cam.ac.uk \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.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).