This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC warnings for unused global variables
"Bonzini" <bonzini@gnu.org> writes:
| > | I also forgot to mention the GCC policy of abandoning a release branch
| > | soon after the .0 release. Software vendors have to chase the GCC
| > | releases to get bug fixed.
| >
| > I cannot let this one pass: We got *four* dot releases from
| > 3.1-branch; the last three were named 3.2.1, 3.2.2, 3.2.3. They all
| > were bug fix releases. Please don't spread misinformation.
|
| I think he was referring to abandoning the 3.2 branch after 3.3.0 is
| released.
OK, then I will explain why I closed the branch before 3.3.0 is released.
Until last week we had threee active branches, with clearly not enough
resources to track them all at the same time. At that point, it was
felt that maintaining 3.2 branch active was wasting resources.
Several times before 3.2.3 went out, I mentioned the fact that I will
propose to close gcc-3_2-branch after the release. Nobody expressed
disagreements, that for a long time. I find it a bit strange to
complain now after the fact whereas there was plenty opportunities to
raise concerns before.
If people feel that they have strong interests in some things, I believe
they should act so as to make them happen.
-- Gaby