Re: Merged CVS repository of gcc and old-gcc

[Volker Reichelt <reichelt at igpm dot rwth-aachen dot de>]

Ian Lance Taylor wrote in http://gcc.gnu.org/ml/gcc/2005-07/msg00625.html:

> In preparation for the future transition to subversion, I've written
> some code to merge the old-gcc repository into current mainline.  I
> would like to see this merged repository used as the basis for the
> conversion to subversion.  The advantage is that it provides revision
> history back to 1992, when the gcc sources were first put into a
> source code control system.  (At the time, it was RCS.  Before 1992
> the source code control system was emacs numbered backup files.)
> 
> Since I just wrote this code, I'd like any feedback that people care
> to give on the correctness and usability of the generated repository.
> People with SSH access to sourceware should be able to access the
> temporary merged repository by doing
>     cvs -d :ext:gcc.gnu.org:/pool/ian/repo co gcc

[snip]

> By the way, in case anybody asks, I will not be doing this merge
> before the subversion conversion, because it changes all the CVS
> revision numbers and thus breaks all existing working directories.

What will happen to the (revision number based) hyperlinks to patches
in Bugzilla and the gcc-cvs mailing list archive like the following:

http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/reg-stack.c.diff?cvsroot=gcc&r1=1.188&r2=1.189

Will they still point to something useful?
If not, that would render the whole gcc-cvs archive list useless. :-(

Well, this is a question for the cvs to svn conversion in general,
but gets more complicated with your merge of the cvs repositories.

Regards,
Volker