From: Volker Reichelt <reichelt@igpm.rwth-aachen.de>
To: gcc@gcc.gnu.org
Cc: mark@codesourcery.com
Subject: Re: What are the chances of another release from gcc-3_2-branch?
Date: Fri, 20 Dec 2002 09:02:00 -0000 [thread overview]
Message-ID: <200212201331.OAA68932@numa6.igpm.rwth-aachen.de> (raw)
I'm all in favor for a 3.2.2 release, but I would suggest to wait with a
release until more bugs get fixed.
Currently we have about 34 bugs in GNATS that are marked as 3.2/3.3
regressions. Since (hopefully) many of them will be fixed for 3.3 anyway,
it would be nice to have the patches backported for the 3.2 branch
(at least the easy ones).
Even releasing 3.2.2 a couple of weeks after 3.3 in order not to have
two releases in the same timeframe would be fine IMHO.
Regards,
Volker
next reply other threads:[~2002-12-20 12:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-20 9:02 Volker Reichelt [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-28 3:47 John David Anglin
2002-12-27 23:58 Michael Elizabeth Chastain
2002-12-19 15:23 Michael Elizabeth Chastain
2002-12-19 13:15 Kaveh R. Ghazi
2002-12-19 15:25 ` Tom Tromey
2002-12-19 22:13 ` Kaveh R. Ghazi
2002-12-15 21:46 Michael Elizabeth Chastain
2002-12-19 0:15 ` Phil Edwards
2002-12-19 11:31 ` Mark Mitchell
2002-12-19 13:19 ` Joe Buck
2002-12-19 15:16 ` Eric Botcazou
2002-12-27 13:21 ` Gabriel Dos Reis
2002-12-27 12:46 ` Gerald Pfeifer
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=200212201331.OAA68932@numa6.igpm.rwth-aachen.de \
--to=reichelt@igpm.rwth-aachen.de \
--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).