From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: "David O'Brien" <obrien@freebsd.org>
Cc: "H. J. Lu" <hjl@lucon.org>, <gcc@gcc.gnu.org>
Subject: Re: Is the gcc-3_3-branch creation still on target?
Date: Fri, 04 Oct 2002 10:28:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.44.0210041904250.24321-100000@naos.dbai.tuwien.ac.at> (raw)
In-Reply-To: <20021004170239.GC19779@dragon.nuxi.com>
On Fri, 4 Oct 2002, David O'Brien wrote:
>> As long as they are fixed in gcc 3.3, I am happy.
> That is the stance I am starting to take. But no one is answering the
> main question of when will the branch be created.
I understood there has been some consensus to possibly delay generating
to branch to allow mainline to further stabilize before the branch.
As Zack mentioned, also 3.2.1 might be delayed to allow further back-
porting a problems already fixed and to be fixed on mainline.
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next prev parent reply other threads:[~2002-10-04 17:06 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 8:23 David O'Brien
2002-10-04 8:50 ` H. J. Lu
2002-10-04 9:29 ` David O'Brien
2002-10-04 9:34 ` H. J. Lu
2002-10-04 9:44 ` David O'Brien
2002-10-04 9:47 ` H. J. Lu
2002-10-04 9:53 ` David O'Brien
2002-10-04 10:02 ` H. J. Lu
2002-10-04 10:23 ` David O'Brien
2002-10-04 10:28 ` Gerald Pfeifer [this message]
2002-10-04 10:06 ` Zack Weinberg
2002-10-04 10:25 ` Gerald Pfeifer
2002-10-04 9:36 ` Andreas Jaeger
2002-10-04 9:46 ` David O'Brien
2002-10-04 10:49 ` Andreas Jaeger
2002-10-04 10:51 ` Jan Hubicka
2002-10-04 11:27 ` Alexander Kabaev
2002-10-04 15:02 ` Richard Henderson
2002-10-04 13:40 ` David O'Brien
2002-10-04 14:31 ` Joseph S. Myers
2002-10-09 1:40 ` David O'Brien
2002-10-09 14:43 ` Joe Buck
2002-10-09 21:04 ` David O'Brien
2002-10-04 10:47 ` Gerald Pfeifer
2002-10-04 10:50 ` Jan Hubicka
2002-10-04 10:58 ` Andreas Jaeger
2002-10-04 11:29 ` Zack Weinberg
2002-10-04 13:47 ` David O'Brien
2002-10-04 15:23 ` Jan Hubicka
2002-10-04 11:18 ` Phil Edwards
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=Pine.BSF.4.44.0210041904250.24321-100000@naos.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=gcc@gcc.gnu.org \
--cc=hjl@lucon.org \
--cc=obrien@freebsd.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).