gcl-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gcl-devel] migration to git


From: Raymond Toy
Subject: Re: [Gcl-devel] migration to git
Date: Thu, 18 Jul 2013 12:39:21 -0700
User-agent: Gnus/5.101 (Gnus v5.10.10) XEmacs/21.5-b33 (linux)

>>>>> "Camm" == Camm Maguire <address@hidden> writes:

    Camm> Greetings!  Here is the script I'm using for the conversion:
    Camm> #!/bin/bash

    Camm> rsync -av vcs.sv.gnu.org::sources/gcl/ ./gclr/
    Camm> cvs2git --blobfile=b --dumpfile=d --username=cvs2git ./gclr/
    Camm> cat d | ./gcl.committers >do
    Camm> rm -rf gcl.git
    Camm> mkdir gcl.git
    Camm> cd gcl.git
    Camm> git init --bare
    Camm> cat ../b ../do | git fast-import
    Camm> ../git-move-refs.py
    Camm> git gc --prune=now
    Camm> cd ..
    Camm> rm -rf gcl
    Camm> git clone ./gcl.git

    Camm> This appears to leave several automatically generated branches in the
    Camm> repository, e.g. unlabeled-1.1.1.1.12, despite the automatic removal
    Camm> attempt.  What should be done here?

My personal feeling is that you do a reasonable job and then just give
up.  At a certain point, the old stuff doesn't matter very much
because you rarely ever use it except to see how the code used to be.

When I converted cmucl cvs to git, a few mistakes were made, like cvs
branches that weren't git branches and some tags weren't correctly
applied.  But I found that those didn't really matter because I never
look back that far anymore since those branches were essentially dead
and most of the bad tags didn't matter because the important tags were
correct.

Ray




reply via email to

[Prev in Thread] Current Thread [Next in Thread]