Message ID | alpine.LNX.2.00.1010260031470.27082@pulcherrima.dbai.tuwien.ac.at |
---|---|
State | New |
Headers | show |
> Andi, are you doing the backport of the removal patch to the 4.5, 4.4 > and 4.3 branches? I'm not sure that has been approved? -Andi
On Tue, 26 Oct 2010, Andi Kleen wrote: >> Andi, are you doing the backport of the removal patch to the 4.5, 4.4 >> and 4.3 branches? > I'm not sure that has been approved? Well, I think it's kind of obvious that we need this for the receiver side of reports submitted via gccbug does not exist any more. We cannot remove that script from existing releases and installations but should make sure any future ones (even from older release branches) avoid that. Gerald
Index: branching.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/branching.html,v retrieving revision 1.28 diff -u -r1.28 branching.html --- branching.html 25 Oct 2010 20:32:57 -0000 1.28 +++ branching.html 25 Oct 2010 22:32:26 -0000 @@ -71,11 +71,6 @@ release on the branch. For example, when branching 3.4, create a milestone for 3.4.1 for PRs that can't be fixed in time for 3.4.0.</li> -<li>For versions of GCC before 4.6.0, update the email parsing script -in CVS at <code>wwwdocs/bugzilla/contrib/bug_email.pl</code>. -Search for an existing version (like "3.3"), and update both places -it occurs to handle the new version through copy and paste.</li> - <li>Ask Daniel Berlin to adjust all PRs with the just-branched version in their summary to also contain the new version corresponding to mainline.</li>