From: Joe Buck <jbuck@synopsys.COM>
To: mark@codesourcery.com (Mark Mitchell)
Cc: jbuck@synopsys.COM (Joe Buck),
gcc-announce@gcc.gnu.org (gcc-announce@gcc.gnu.org),
gcc@gcc.gnu.org (gcc@gcc.gnu.org)
Subject: Re: GCC 3.0.4 Released
Date: Thu, 21 Feb 2002 18:12:00 -0000 [thread overview]
Message-ID: <200202220206.SAA16540@atrus.synopsys.com> (raw)
In-Reply-To: <74700000.1014340882@warlock.codesourcery.com> from "Mark Mitchell" at Feb 21, 2002 05:21:22 PM
> > Cool. Could someone (Gerald?) update the gcc.gnu.org main web page
> > News/Announcements?
>
> I just did it.
You added the announcement, but the page still says, just above, that
3.0.3 is the latest release.
next prev parent reply other threads:[~2002-02-22 2:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-21 16:45 Mark Mitchell
2002-02-21 16:48 ` Joe Buck
2002-02-21 17:24 ` Mark Mitchell
2002-02-21 18:12 ` Joe Buck [this message]
2002-02-21 17:21 ` Joseph S. Myers
2002-02-21 17:26 ` Mark Mitchell
2002-02-21 17:42 ` Joseph S. Myers
2002-02-21 17:50 ` Joe Buck
2002-02-21 17:56 ` Joseph S. Myers
2002-02-21 18:07 ` Joe Buck
2002-02-22 1:51 ` Joseph S. Myers
2002-02-22 2:32 ` Jakub Jelinek
2002-02-21 18:33 ` Mark Mitchell
2002-02-21 17:13 the_sage2000
2002-02-22 2:57 Toon Moene
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=200202220206.SAA16540@atrus.synopsys.com \
--to=jbuck@synopsys.com \
--cc=gcc-announce@gcc.gnu.org \
--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).