| Submitter | Gerald Pfeifer |
|---|---|
| Date | Oct. 25, 2010, 8:33 p.m. |
| Message ID | <alpine.LNX.2.00.1010252230030.27082@pulcherrima.dbai.tuwien.ac.at> |
| Download | mbox | patch |
| Permalink | /patch/69139/ |
| State | New |
| Headers | show |
Comments
On Mon, 25 Oct 2010, Gerald Pfeifer wrote: > I believe Joseph was requesting something like the patch below > which I am installing now. No, because this is nothing to do with the version of GCC. The script in question no longer exists in the current installation; the CVS repository directory for Bugzilla is no longer in place; if the gccbug removal patch hasn't been backported to the actice release branches it should be; and both releasing.html and branching.html have/had references to this contrib/ script that should go away.
Patch
Index: branching.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/branching.html,v retrieving revision 1.27 diff -u -r1.27 branching.html --- branching.html 25 Oct 2010 18:25:12 -0000 1.27 +++ branching.html 25 Oct 2010 20:31:37 -0000 @@ -71,8 +71,8 @@ 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>Update the email parsing script to handle bugs against the new versions. -The script is in CVS at <code>wwwdocs/bugzilla/contrib/bug_email.pl</code>. +<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>