On Fri, 2005-12-23 at 06:43 -0400, [EMAIL PROTECTED] wrote: > > My lesser problem is that tailor fails to recognize when all the changes > > to a repository are in fact in the same state, the only recent changes > > having been due to syncing. So I can sync from cvs to svn and back again > > forever, each time getting a long list of changes. It seems like I must > > be missing something. If you do a svn diff -rX:Y file:///repo you can > > see that there have been no actual changes. > > This is the problem described in this thread: > > http://lists.zooko.com/pipermail/tailor/2005-December/000278.html > > There is no currently-implemented general solution, and the best idea that > I have come up with [1] requires that darcs be one of the two systems. > > [1] http://progetti.arstecnica.it/tailor/wiki/TwoWaySync > > On the other hand, if you learn some more about how tailor uses the underlying > systems then you could manually babysit it and then you wouldn't need the > generality and robustness outlined in [1].
Ah, thanks. I am intrigued by darcs, but unfortunately the rest of my organization is less willing to experiment with infrastructure. Fortunately, the changes will mostly be coming from cvs to subversion with only the occasional merge pushing things back. I think we can live with that. David > > Regards, > > Zooko _______________________________________________ Tailor mailing list [email protected] http://lists.zooko.com/mailman/listinfo/tailor
