I've been evaluating tailor recently, and have noticed a few limitations it'd be great to clarify, as on the whole it's the nicest (partial) solution I've found yet.
Firstly, tailor doesn't seem to understand history-preserving copies. Everything seems to be an add, delete or modify. This leads to my next query, namely, are tags/branches actually supported? I was led to believe they were (even if actual copy-tracking wasn't), but the result of every copy is going into my new repository as a new addition. Looking in the debug output, all I ever see is a checkout, followed by an rsync, then a commit (then the propsets). Is the destructive use of rsync required when the full history is available in the log (to re-enact)? The main advantage I wanted from tailor was to provide me full access to the history of the vendor code I'm importing when merging in my own repository, but without copy history it kind of falls down slightly in that regard. It's still better than a en-masse code import, but not quite what I thought it was capable of initially :( I was kind of expecting tailor to checkout a revision, read the log actions, replay them, then check in the result and fix up anything required (author, date, etc). So, can anyone shed any light on the state of play of the Subversion support in Tailor for me please? (and hopefully tell me I'm a fool and am simply doing things wrong and it all actually works! :)) - Jamie
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Tailor mailing list [email protected] http://lists.zooko.com/mailman/listinfo/tailor
