CVS to Git migration

Ben Walton bdwalton-Re5JQEeQqe8AvxtiuMwx3w at public.gmane.org
Tue Apr 23 06:48:38 UTC 2013


You could also import the cvs history to git with the initial import. Tag
that import as cvs-orig or something and then in a second commit, wrote out
the cvs meta data.

I've never used cvs2git but if you send this query to the git mailing list
I'm sure you'll find a workable (less ugly) solution. The list is quite
open and friendly.

Hth.
-Ben
On Apr 23, 2013 12:42 AM, "Neil Watson" <tlug-neil-8agRmHhQ+n2CxnSzwYWP7Q at public.gmane.org> wrote:

> I did a CVS to SVN conversion years ago. If I were to do it again using
> Git or any other RCS I would not convert. The conversion process can
> leave you uncertain about the integrity of converted history. Instead, I
> would retire CVS as an archive and start new with Git.
>
> --
> Neil Watson
> Linux/UNIX Consultant
> http://watson-wilson.ca
> --
> The Toronto Linux Users Group.      Meetings: http://gtalug.org/
> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
> How to UNSUBSCRIBE: http://gtalug.org/wiki/**Mailing_lists<http://gtalug.org/wiki/Mailing_lists>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gtalug.org/pipermail/legacy/attachments/20130423/603f062a/attachment.html>


More information about the Legacy mailing list