{"thread":{"id":"2531","subject":"A case for tailor","startedAt":"2005-11-15T18:48:09Z","lastAt":"2005-11-17T12:02:54Z","messageCount":5,"participants":["Johannes Schindelin","Martin Langhoff","Matthias Urlichs"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"11921","messageId":"Pine.LNX.4.63.0511151931001.1157@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"2531","inReplyTo":null,"subject":"A case for tailor","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2005-11-15T18:48:09Z","receivedAt":"2005-11-15T18:48:09Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nI was trying to import a project into git, the upstream of which is \nmanaged by Subversion. There has been a flurry of enhancements to \ngit-svnimport, so I thought I´d give it a try.\n\nShort version: it did not work.\n\nLonger version: depending on the argument to \"-T\", it stopped right away, \nor it stopped after about 60 commits. Right at the beginning, a lot of \nwarnings told me about some files not being where they were expected.\n\nPossible explanation: at some early stage, the trunk was named \"trunk\", \nbut somehow (don´t ask me how, I am a fan of git, not svn) renamed to \n\"head\".\n\nWell, could also be cygwin, which I am stuck with in my office. \n\nBTW, I noticed that the manpage tells me that \"-t\" should be used to \nspecify the trunk, but the program (and it´s usage message) disagree.\n\nEnter tailor. It is a program written in python, which is meant to convert \nrepositories between different SCM formats. It was mentioned some time ago \non this list, supports svn import and git export, so I thought I´d give \nthat a try.\n\nShort version: it worked.\n\nLonger version: I had to fix a little bug which made git ignore the \nauthor_date (only to find that this had been fixed in the current devel \nversion of tailor), had to make sure .git/info existed, and I added a \ndirty workaround to git so that empty commits would not lead to a \nscreeching halt of the conversion.\n\nComparing the speeds, I´d also say that they are comparable, maybe \ngit-svnimport is just a tad faster (until it fscks up).\n\nI am right now trying to convert tailor´s repository (since I don´t like \nto keep it in the darcs (pun intended) format). However there is still a \nlittle problem with darcs, which is probably a problem with the operating \nsystem.\n\nJust wanted to let people know...\n\nCiao,\nDscho\n"},{"id":"11930","messageId":"46a038f90511151259l51d13181j670274e123d7610f@mail.gmail.com","threadId":"2531","inReplyTo":"Pine.LNX.4.63.0511151931001.1157@wbgn013.biozentrum.uni-wuerzburg.de","subject":"Re: A case for tailor","fromName":"Martin Langhoff","fromEmail":"martin.langhoff@gmail.com","sentAt":"2005-11-15T20:59:17Z","receivedAt":"2005-11-15T20:59:17Z","isPatch":false,"sender":{"key":"martin.langhoff@gmail.com","avatar":"https://gravatar.com/avatar/1e3f311b6c4c15836501901ca58f8c0b0667246488084ba524d8bc9867e22fd9?d=mp&s=160"},"body":"On 11/16/05, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:\n> Just wanted to let people know...\n\nI've checked out tailor a while ago, and it seems a quite capable\ntool. Even bounced a few emails with the author, because I thought\nthat we could perhaps deprecate our imports scripts. It _is_ good, and\nseems to have a cool community around it.\n\nThe short of it is that tailor won't do branches. So for trivial\nsingle-line-of-development projects, you're fine with it, probably\neven happier than with our import scripts.  Sadly, none of the\nprojects I've worked in the last 6 years fall into that category ;-)\n\ncheers,\n\n\nmartin\n"},{"id":"11939","messageId":"Pine.LNX.4.63.0511152242330.2354@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"2531","inReplyTo":"46a038f90511151259l51d13181j670274e123d7610f@mail.gmail.com","subject":"Re: A case for tailor","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2005-11-15T21:43:51Z","receivedAt":"2005-11-15T21:43:51Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Wed, 16 Nov 2005, Martin Langhoff wrote:\n\n> The short of it is that tailor won't do branches. So for trivial\n> single-line-of-development projects, you're fine with it, probably\n> even happier than with our import scripts.  Sadly, none of the\n> projects I've worked in the last 6 years fall into that category ;-)\n\nI wasn´t aware of that. However, I am luckier than you are: only a few \nrelease+bugfix branches, none of which are of interest right now.\n\nCiao,\nDscho\n"},{"id":"12064","messageId":"pan.2005.11.16.23.40.20.119887@smurf.noris.de","threadId":"2531","inReplyTo":"Pine.LNX.4.63.0511151931001.1157@wbgn013.biozentrum.uni-wuerzburg.de","subject":"Re: A case for tailor","fromName":"Matthias Urlichs","fromEmail":"smurf@smurf.noris.de","sentAt":"2005-11-16T23:40:20Z","receivedAt":"2005-11-16T23:40:20Z","isPatch":false,"sender":{"key":"matthias@urlichs.de","avatar":"https://gravatar.com/avatar/2708905af227313eba6f2b2ae0f7d0259b5ac5d71baef58fe5a13c699ce0bbf0?d=mp&s=160"},"body":"Hi, Johannes Schindelin wrote:\n\n> Possible explanation: at some early stage, the trunk was named \"trunk\", \n> but somehow (don´t ask me how, I am a fan of git, not svn) renamed to \n> \"head\".\n\nWell, you *could* use \"-T trunk\" to import the first part, ^C when it\nstarts complaining about 'head', duplicate the last line of .git/svn2git\n(incrementing the SVN change number), and continue with \"-T head\".\n\nThat hackery sortof depends on Upstream not changing anything *else* while\nrenaming 'trunk' to 'head' ...\n\nOf course, the second possibility is to allow patterns as prefixes, drop\nthe distinction of \"trunk\" and \"branch\", and store the refs as full\npaths under .git/refs/heads/**. You're welcome to submit a patch; please\ndon't forget backwards compatibility for those poor souls who need to do\nincremental imports. ;-)\n\n-- \nMatthias Urlichs   |   {M:U} IT Design @ m-u-it.de   |  smurf@smurf.noris.de\nDisclaimer: The quote was selected randomly. Really. | http://smurf.noris.de\n - -\nGot a dictionary?  I want to know the meaning of life.\n"},{"id":"12097","messageId":"Pine.LNX.4.63.0511171300350.2104@wbgn013.biozentrum.uni-wuerzburg.de","threadId":"2531","inReplyTo":"pan.2005.11.16.23.40.20.119887@smurf.noris.de","subject":"Re: A case for tailor","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2005-11-17T12:02:54Z","receivedAt":"2005-11-17T12:02:54Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Thu, 17 Nov 2005, Matthias Urlichs wrote:\n\n> Hi, Johannes Schindelin wrote:\n> \n> > Possible explanation: at some early stage, the trunk was named \"trunk\", \n> > but somehow (don´t ask me how, I am a fan of git, not svn) renamed to \n> > \"head\".\n> \n> Well, you *could* use \"-T trunk\" to import the first part, ^C when it\n> starts complaining about 'head', duplicate the last line of .git/svn2git\n> (incrementing the SVN change number), and continue with \"-T head\".\n> \n> That hackery sortof depends on Upstream not changing anything *else* while\n> renaming 'trunk' to 'head' ...\n> \n> Of course, the second possibility is to allow patterns as prefixes, drop\n> the distinction of \"trunk\" and \"branch\", and store the refs as full\n> paths under .git/refs/heads/**. You're welcome to submit a patch; please\n> don't forget backwards compatibility for those poor souls who need to do\n> incremental imports. ;-)\n\n;-), too.\n\nIt is not *that* important for me, as that particular project is linear. \nIt is not even important to convert it to git, but I like to pickaxe the \nsource (why not let the machine do the work for you?).\n\nSo I will probably not work on svn->git end any more...\n\nCiao,\nDscho\n"}]}