public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mark Mitchell <mark@codesourcery.com>
To: gcc@gcc.gnu.org
Subject: GCC 3.4 branch frozen
Date: Sat, 30 Oct 2004 22:28:00 -0000	[thread overview]
Message-ID: <4183EB2C.1030103@codesourcery.com> (raw)

As of now, please consider the GCC 3.4 branch frozen.

I will be making a pass over the open PRs, and then, hopefully, spinning 
a release candidate tomorrow.

-- 
Mark Mitchell
CodeSourcery, LLC
mark@codesourcery.com

             reply	other threads:[~2004-10-30 19:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-30 22:28 Mark Mitchell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-08-29 21:46 Mark Mitchell
2004-08-29 23:21 ` H. J. Lu
2004-08-29 23:40   ` Mark Mitchell
2004-08-30  7:06     ` H. J. Lu
2004-08-30  7:10       ` Mark Mitchell
2004-04-19  0:27 GCC 3.4 Branch Frozen Michael Elizabeth Chastain
2004-04-19  1:26 ` Mark Mitchell
2004-04-18 22:58 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=4183EB2C.1030103@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).