This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Details for svn test repository
On Thu, 10 Feb 2005, Daniel Berlin wrote:
> The only way to properly do this then is to just hack up the rcs files
> with the old-gcc data, where approriate, and increment all the other
> revision numbers.
So does anyone wish to write a pre-pass which hacks up the old-gcc and gcc
RCS files into something good to pass to cvs2svn (which could then be used
as a stage in future trial conversions, and the final conversion)?
To my mind some sort of detection of file renames is at least as desirable
as doing anything with old-gcc; after all, the history that file renames
make more difficult to see is mostly more recent than that in old-gcc.
(And I've long argued that we shouldn't hold up rearrangements involving
moving files on the grounds that this confuses history because we can live
with the confusion for now and it could all be sorted out in the convertor
to a new system.) <http://cvs2svn.tigris.org/issues/show_bug.cgi?id=1>
has lots of discussion of how to auto-detect renames but though
auto-detection would be useful I think that most of the important cases in
GCC could be handled through a manual hints file with entries like
gcc/install.texi -> gcc/doc/install-old.texi
where if a changeset (for mainline or any branch) removes the first named
file and adds the second named file, this is taken as a rename
(copy+delete).
--
Joseph S. Myers http://www.srcf.ucam.org/~jsm28/gcc/
jsm@polyomino.org.uk (personal mail)
joseph@codesourcery.com (CodeSourcery mail)
jsm28@gcc.gnu.org (Bugzilla assignments and CCs)