[Followup] hg-cvs-import

[Edouard Gomez]

Benoit Boissinot <bboissin <at> gmail.com> writes:
> What do you mean by boostraping ? can you explain more ?

Last time i tried convert-repo, the initial import is still to be done manually.

In the case of GIT, i had to "git log" to see the first commit ref, and then
update to that commit ref and finally bootstrap the conversion process creating
the hg repo with:
$ hg init .
$ echo .git > .hgignore
$ hg add
$ hg commit -m "Initial import into mercurial"
$ hg tip -q --debug |grep changeset|cut -d ':' -f 3 > map
$ vi map (to add the git node hash as well)

One big problem here: project history is not respected. Date, commiter, message
are not the same. The UI change in latest 0.9 makes things easier for date now,
and nothing prevents me from really importing the first commit with date, user
and message correctly set, but still i have to take care of all this.

For CVS, i tried to bootstrap from scratch (well at least with the cvsps file
:-)), and it failed because initial commit wasn't there.

hg-cvs-import takes care of bootstraping the conversion process, git-cvsimport
does too, cvs2svn does as well, tailor does also... i think it's a big miss in
convert-repo.

--
Edouard Gomez