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.0.3
Date: Wed, 21 Nov 2001 18:24:00 -0000	[thread overview]
Message-ID: <13880000.1007057994@warlock.codesourcery.com> (raw)

Please remember that Dec 1. is the freeze date for changes going into
GCC 3.0.3.  Non-documentation changes will require my approval after
that point.

I have received some important bug reports from people.  I will be
posting a list of those shortly.  We will try to fix these before the
release if possible.

Thank you,

-- 
Mark Mitchell                mark@codesourcery.com
CodeSourcery, LLC            http://www.codesourcery.com

WARNING: multiple messages have this Message-ID

From: Mark Mitchell <mark@codesourcery.com>
To: gcc@gcc.gnu.org
Subject: GCC 3.0.3
Date: Thu, 29 Nov 2001 10:24:00 -0000	[thread overview]
Message-ID: <13880000.1007057994@warlock.codesourcery.com> (raw)
Message-ID: <20011129102400.zt3ybSQs5UH28TbG9lJSnbz3bxP7HpvwAom4ICwE9o8@z> (raw)

Please remember that Dec 1. is the freeze date for changes going into
GCC 3.0.3.  Non-documentation changes will require my approval after
that point.

I have received some important bug reports from people.  I will be
posting a list of those shortly.  We will try to fix these before the
release if possible.

Thank you,

-- 
Mark Mitchell                mark@codesourcery.com
CodeSourcery, LLC            http://www.codesourcery.com

             reply	other threads:[~2001-11-29 18:24 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-21 18:24 Mark Mitchell [this message]
2001-11-21 22:25 ` Joe Buck
2001-11-21 23:26   ` Mark Mitchell
2001-11-22  0:04     ` Joe Buck
2001-11-22  0:14       ` Mark Mitchell
2001-11-22  2:58         ` Joe Buck
2001-11-22  7:35           ` Mark Mitchell
2001-11-29 17:16             ` Mark Mitchell
2001-11-29 16:15           ` Joe Buck
2001-11-29 14:25         ` Mark Mitchell
2001-11-29 13:51       ` Joe Buck
2001-11-29 12:28     ` Mark Mitchell
2001-11-23 14:47   ` fix for PR 4447: is this really correct? Joe Buck
2001-11-24 20:36     ` Kriang Lerdsuwanakij
2001-11-30 23:02       ` Kriang Lerdsuwanakij
2001-12-01 16:08       ` Joe Buck
2001-12-02  3:12         ` Kriang Lerdsuwanakij
2001-12-03  9:42           ` Mark Mitchell
2001-12-01 17:32       ` Alexandre Oliva
2001-11-30 11:20     ` Joe Buck
2001-11-29 11:51   ` GCC 3.0.3 Joe Buck
2001-11-23 14:48 ` Stephane Carrez
2001-11-23 15:52   ` Jakub Jelinek
2001-11-30 11:47     ` Jakub Jelinek
2001-11-30 11:27   ` Stephane Carrez
2001-12-03  8:34   ` Mark Mitchell
2001-11-24 21:15 ` Toon Moene
2001-11-30 23:39   ` Toon Moene
2001-11-29 10:24 ` 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=13880000.1007057994@warlock.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).