This metabug is used to track all the patches which have been written during Stage 3 of GCC 4.0 but do not qualify for that stage, and are waiting for Stage 1 of GCC 4.1 to be applied. Please, do not attacch the patches to this bug. Open a new bug report, and mark it as "blocking" this metabug (this metabug will "depend" on the new bug report).
Not really interesting any more since 4.0 has branched.
> Not really interesting any more since 4.0 has branched That is nonsense. This is the meta-bug used to track stuff that didn't make it into 4.0 but shouldn't miss 4.1 too.
(In reply to comment #2) > > Not really interesting any more since 4.0 has branched > > That is nonsense. This is the meta-bug used to track stuff that didn't make > it into 4.0 but shouldn't miss 4.1 too. Yes but really it was only useful when 4.0 was the mainline and nothing else. Since we are now in Stage 1, it no longer applies.
I agree with Joerne. This bug was opened to track things that had to be revaluated when 4.1 stage 1 opens, so it has to be kept open until its list of dependencies is finished. It remembers us that there are bugs with patches waiting for review since *long* time. Instead, it does not make sense to add *new* bugs to it. Joerne, by adding bugs here you are not making them "important" for 4.1 in any sense. If they are regressions, you should mark them as such in the summary with the [Regression] stomp, and modify the target milestone to 4.1. Otherwise, just keep them open with the "patch" keyword (assuming they have a patch) and ping reviews as usual. This is pretty clearly stated in the original bug description: > This metabug is used to track all the patches which have been > written during Stage 3 of GCC 4.0 but do not qualify for that > stage, and are waiting for Stage 1 of GCC 4.1 to be applied. Would you mind removing from this bug all those bugs which do not fit this description (opened after 4.0 branched)? Thanks.
(In reply to comment #4) > This is pretty clearly stated in the original bug description: > > > This metabug is used to track all the patches which have been > > written during Stage 3 of GCC 4.0 but do not qualify for that > > stage, and are waiting for Stage 1 of GCC 4.1 to be applied. > > Would you mind removing from this bug all those bugs which do not fit this > description (opened after 4.0 branched)? Thanks. These are two different things. I kept with the original description of the bug, I.e. adding bugs for which patches have been written during gcc 4.0 or earlier. Some already already had a bug submitted to bugzilla, so I only had to create the link for the bug; others had been posted separately to gcc-patches, but didn't have a bugzilla bug to track them, for these I have added the bugzilla bug. Some of these were posted, but the archive was damaged so the patches can only be found in the google cache, so that needed reposting too. And then there is a third class where the patches have previously be only posted in bulk. I would have worked on them in 4.0 stage three, if it hadn't been for the absolute code freeze. If you can't even get regression bugfixes accepted, there is no point posting any more. All categories patches might need some tweaks to work in 4.1, this is why I write some new code even for patches that are several years old.
What should be done with this meta-bug? The remaining pending patches are all large patches from Joern that add new functionality, but they do not fix regressions. Move forward to 4.2?
Subject: Re: [meta-bug] GCC 4.1 pending patches On Thu, 2005-10-13 at 20:38 +0000, steven at gcc dot gnu dot org wrote: > > ------- Comment #6 from steven at gcc dot gnu dot org 2005-10-13 20:38 ------- > What should be done with this meta-bug? The remaining pending patches > are all large patches from Joern that add new functionality, but they > do not fix regressions. Move forward to 4.2? Yea, if they're still useful, definitely move them to the 4.2 pending patches metabug. jeff
Subject: Re: [meta-bug] GCC 4.1 pending patches steven at gcc dot gnu dot org wrote: > ------- Comment #6 from steven at gcc dot gnu dot org 2005-10-13 20:38 ------- > What should be done with this meta-bug? The remaining pending patches > are all large patches from Joern that add new functionality, but they > do not fix regressions. Move forward to 4.2? Yes, please. Thanks,
Fixed. I moved the remaining open ones to the 4.2 pending patches meta-bug.