On 03/02/2012 03:02 PM, Jakub Jelinek wrote:
releasing.html is wrong for this, it has nothing to do with releasing, but with branching, so something like that should go into branching.html instead. From this isn't clear where this command needs to be run, btw, on gcc.gnu.org directly, somewhere else?
Thanks for the comments - I unfortunately saw them only just after Richard's OK. How about the following?
Tobias
Index: releasing.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/releasing.html,v retrieving revision 1.37 diff -u -r1.37 releasing.html --- releasing.html 2 Mar 2012 14:04:38 -0000 1.37 +++ releasing.html 2 Mar 2012 14:08:28 -0000 @@ -55,12 +55,6 @@ <li>Reenable the generation of snapshots off the respective release branch in the crontab of gccadmin on gcc.gnu.org.</li> - -<li>For a new major release, add the release to GIT mirror; example: -<pre> -$ cd /git/gcc.git/.git -$ git symbolic-ref refs/heads/gcc-4_7-branch refs/remotes/gcc-4_7-branch -</pre></li> </ol> <h2>Web Site Updates</h2> Index: branching.html =================================================================== RCS file: /cvs/gcc/wwwdocs/htdocs/branching.html,v retrieving revision 1.30 diff -u -r1.30 branching.html --- branching.html 20 Nov 2010 15:15:51 -0000 1.30 +++ branching.html 2 Mar 2012 14:08:28 -0000 @@ -23,6 +23,17 @@ <li>Update the file <code>gcc/BASE-VER</code> on the mainline, to use the next major release number (e.g., 3.2 instead of 3.1).</li> +<li>Update the GIT mirror by running on <code>gcc.gnu.org</code> the +following command, substituting appropriate version +numbers: +<blockquote> +<pre> +$ cd /git/gcc.git/.git +$ git symbolic-ref refs/heads/gcc-4_7-branch refs/remotes/gcc-4_7-branch +</pre> +</blockquote> +</li> + <li>Create a new <code>htdocs/gcc-<var>VERSION</var></code> directory for the next major release in the <code>wwwdocs</code> repository and populate it with initial copies of <code>changes.html</code> and
