Lele Gaifax wrote: >> - the change to tailor.py to avoid loosing the initial commit log on >> the imported branch probably breaks all other targets because of the >> previous issue > > Uhm, I did not understand, but I'll look at the diff again.
When parsing parent-branch I set an attribute in the git target object, and I use it subsequently in generic code. I'm no python expert, but in perl it would be "undef" with any other target, and the comparison would produce an exception. >> - I could not make the cvsps source work to verify it fetches tags >> better than the cvs one > > Care to report the problem? I'll stick a note on attaching some test > cases for cvsps... I'll do that tonight. >> - the "projects" parameter has to be specified explicitely to force >> the ordering of branch imports - I would have expected the declaration >> order to be used. > > Eh, silly ConfigParsers :-| No way to force an order with those things ? > Yes, this is really something I'd like to improve, This is even planned > for http://progetti.arstecnica.it/tailor/milestone/VersionTwo. Cool. Note: I noticed the desctiption for the VersionOne milestone is really outdated. >> Comparison with git-cvsimport [...] > Good! I took the liberty of adding this to > http://progetti.arstecnica.it/tailor/wiki/GitRepository, hope that's ok. Well, I fear it will have to be reshaped for anyone to understand this :) Best regards, -- Yann Dirson <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> _______________________________________________ Tailor mailing list [email protected] http://lists.zooko.com/mailman/listinfo/tailor
