A case for tailor

Hi,

I was trying to import a project into git, the upstream of which is managed by Subversion. There has been a flurry of enhancements to git-svnimport, so I thought I´d give it a try.

Short version: it did not work.

Longer version: depending on the argument to "-T", it stopped right away, or it stopped after about 60 commits. Right at the beginning, a lot of warnings told me about some files not being where they were expected.

Possible explanation: at some early stage, the trunk was named "trunk", but somehow (don´t ask me how, I am a fan of git, not svn) renamed to "head".

Well, could also be cygwin, which I am stuck with in my office. 

BTW, I noticed that the manpage tells me that "-t" should be used to specify the trunk, but the program (and it´s usage message) disagree.

Enter tailor. It is a program written in python, which is meant to convert repositories between different SCM formats. It was mentioned some time ago on this list, supports svn import and git export, so I thought I´d give that a try.

Short version: it worked.

Longer version: I had to fix a little bug which made git ignore the author_date (only to find that this had been fixed in the current devel version of tailor), had to make sure .git/info existed, and I added a dirty workaround to git so that empty commits would not lead to a screeching halt of the conversion.

Comparing the speeds, I´d also say that they are comparable, maybe git-svnimport is just a tad faster (until it fscks up).

I am right now trying to convert tailor´s repository (since I don´t like to keep it in the darcs (pun intended) format). However there is still a little problem with darcs, which is probably a problem with the operating system.

Just wanted to let people know...

Ciao, Dscho