From: Mark Mitchell <mark@codesourcery.com>
To: gcc@gcc.gnu.org
Subject: GCC 3.3 branch open
Date: Fri, 08 Aug 2003 19:03:00 -0000 [thread overview]
Message-ID: <200308081809.h78I90Z4010155@doubledemon.codesourcery.com> (raw)
The 3.3 branch is now open, under the usual regression-only check-in
rules.
--
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com
next reply other threads:[~2003-08-08 18:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 19:03 Mark Mitchell [this message]
2003-08-08 20:05 ` Kelley Cook
2003-08-08 20:16 ` Mark Mitchell
-- strict thread matches above, loose matches on Subject: below --
2003-10-17 19:30 GCC 3.3 Branch Open Mark Mitchell
2003-10-18 15:53 ` Eric Botcazou
2003-10-20 6:12 ` Mark Mitchell
2003-05-14 23:48 Mark Mitchell
2003-05-15 0:12 ` Daniel Berlin
2003-05-15 10:19 ` Joseph S. Myers
2003-05-15 14:04 ` Daniel Berlin
2003-05-15 15:59 ` Daniel Berlin
2003-05-15 12:41 ` Gerald Pfeifer
2003-05-15 14:08 ` Daniel Berlin
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=200308081809.h78I90Z4010155@doubledemon.codesourcery.com \
--to=mark@codesourcery.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).