On Wed, Jun 06, 2007 at 01:57:53PM -0500, Kelly F. Hickel wrote: > > I have implemented this in the git target - it is rather crude: if the > > tag is not properly imported (not sure why it happens), you have to > > find out for yourself the commit id of the branchpoint, but it works > > for me. > > So, I'm a bit confused. At first I thought that Tailor dealt with > branching, but then I figured out that just means that it can import a > particular branch as a straight-line revision history. If you just > changed the git back end, then how did it "find" the branch points?
It precisely does not "find" them. You have to import the parent branch first, then check if the base tag of the branch has been properly imported, and if not (or if there was no base tag for the cvs branch at all, which is possible), you have to locate yourself in the imported branch the commit id corresponding to the branchpoint. I said it was very crude :) More details (and roadmap to full the branch support you expected) at http://progetti.arstecnica.it/tailor/wiki/GitRepository (hm, the site appears to be not working right now) > We've looked at git (and darcs, mercurial, and so on), we like > monotone.... ;> Oh, OK :) Best regards, -- Yann _______________________________________________ Tailor mailing list [email protected] http://lists.zooko.com/mailman/listinfo/tailor
