This is the mail archive of the
mailing list for the GCC project.
Re: Branching for GCC 3.0
- To: mark at codesourcery dot com
- Subject: Re: Branching for GCC 3.0
- From: Marc Espie <espie at quatramaran dot ens dot fr>
- Date: Mon, 8 Jan 2001 21:23:50 +0100
- Cc: gcc at gcc dot gnu dot org
- Organization: Ecole Normale Superieure (quatramaran)
In article <20010107125803Q.firstname.lastname@example.org> you write:
>Since there is definitely a trend towards major movement on the
>mainline, I think it is appropriate to branch for GCC 3.0 sooner,
>rather than later. Many bug-fix patches will need to go on both
>branches, but all new functionality can go on the mainline, and help
>us keep the release branch stable.
> Questions, comments, theories, or philosophies?
I have some patches for various OpenBSD platforms (including the missing
configuration fragments for ppc and a few others) that I definitely like to
see in gcc 3.0, since these appear to be working (gcc 3.0 bumps
My only problem is that I've been very busy checking patches and verifying
whether 2.95.3 candidate works or not, vax et al.
Since those patches won't hinder the release, I assume they're still okay
even a bit after january 14th, right ?
Otherwise, making the gcc 3.0 branch date almost coincide with the 2.95.3
release date is a bit unfair for those of us with an investment in making
stable releases work...