Joe Buck wrote:
On Tue, Feb 19, 2008 at 10:11:41PM +0100, Ralf Wildenhues wrote:
* Gerald Pfeifer wrote on Tue, Feb 19, 2008 at 10:06:14PM CET:
On Tue, 19 Feb 2008, Ralf Wildenhues wrote:
So does you above OK also extend to the 4.3 branch?
Heh, by committing to the 4.2 branch you made this a regression in 4.3
now. :-} It's not in any GCC 4.2 release yet, so not a high priority
for GCC 4.3.0, I guess, but would be nice to see this in GCC 4.3.1 at
least (after a bit more exposure in HEAD perhaps).
Jakub gave me ok for 4.2 branch, and I committed there.
I guess we're OK as long as 4.3.1 comes out before the next 4.2.x release.
But I think in general we should avoid this kind of thing (creating a
new regression by fixing a bug in 4.2.x and not in 4.3.x).
We really do not want that to happen.
This is also why we decided relatively recently (after the last release)
to try to keep release branches releasing around the same time; in other
words, to avoid releasing 4.3.0 today, 4.2.4 a month later, and 4.3.1
two months after that. That creates a period of time where 4.2.4 may
have a bug fix, but no 4.3.x release does.
Please don't commit patches to one release branch unless you are also
patching all later branches.
Thanks,
--
Mark Mitchell
CodeSourcery
[EMAIL PROTECTED]
(650) 331-3385 x713
