From: | Marko Kreen <markokr(at)gmail(dot)com> |
---|---|
To: | Kris Jurka <books(at)ejurka(dot)com> |
Cc: | Kjetil Nygård <polpot78(at)gmail(dot)com>, Maciek Sakrejda <msakrejda(at)truviso(dot)com>, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Moving to git |
Date: | 2011-10-04 22:04:26 |
Message-ID: | CACMqXCL5Cx98motUx+ZXDqumoAVutttsE4JeaA3WBbqOVMmRow@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Tue, Oct 4, 2011 at 6:39 PM, Kris Jurka <books(at)ejurka(dot)com> wrote:
> On Tue, 4 Oct 2011, Kjetil Nyg?rd wrote:
>> 1. cvsimport keeps the history. It will not be lost.
>
> My experience is that git-cvsimport does not work correctly. Or at least
> it didn't without a patched version of cvsps. Perhaps that's all been
> fixed up, but that's why it's important to do a verification that history
> has been accurately preserved rather than just publishing whatever results
> come out.
>
> http://archives.postgresql.org/pgsql-www/2008-12/msg00124.php
>
> If anyone would like to work on the cvs to git conversion what I would
> like to see is a script/configuration file to invoke the conversion
> utility and then a script to do a comparison between any tag in cvs and
> the corresponding tag in the new git repository.
I also have bad experience with cvsimport - like getting
first commit wrong, problems with tags/branches.
Then I re-imported with cvs2git which worked perfectly,
no messing around was needed.
So I suggest you skip cvsimport and do the import with cvs2git.
--
marko
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2011-10-05 00:42:55 | Re: Moving to git |
Previous Message | Kris Jurka | 2011-10-04 16:39:56 | Re: Moving to git |