On Fri, Mar 2, 2012 at 3:02 PM, Jakub Jelinek <ja...@redhat.com> wrote: > On Fri, Mar 02, 2012 at 03:00:12PM +0100, Tobias Burnus wrote: >> As mentioned on #gcc, the git mirror should also include new major releases. >> >> Diego also documented it on the wiki: >> http://gcc.gnu.org/wiki/GitMirror#Adding_a_branch_to_origin.2BAC8.2A >> (Wiki page rev. 94 -> 96) >> >> OK for committal? > > 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?
Oops, yes. Indeed it belongs in branching.html. >> Index: releasing.html >> =================================================================== >> RCS file: /cvs/gcc/wwwdocs/htdocs/releasing.html,v >> retrieving revision 1.36 >> diff -u -r1.36 releasing.html >> --- releasing.html 1 Mar 2012 13:16:51 -0000 1.36 >> +++ releasing.html 2 Mar 2012 13:55:52 -0000 >> @@ -55,6 +55,12 @@ >> >> <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> > > > Jakub
