On Sun, Dec 18, 2005 at 06:25:26PM -0400, [EMAIL PROTECTED] wrote: > > > Let there be two tailor directories, once which translates patches from > > > svn to > > > darcs (called "SD" from here on) and one which translates patches from > > > darcs to > > > svn (called "DS" from here on). > > > Hmm. It doesn't seem right in my head to need two tailor directories. > > I have been doing two-way sync with a single tailor directory for quite > > some time, it's just a little clunky. > > Do tell! How does it work? What is clunky about it? How do you tell tailor > to first translate patches from subdir ./sw/ to ./dw/, and then later to > translate them from ./dw/ to ./sw/?
Hmm. My updates to the wiki from 11 or 12 April seem to have vanished, at least I don't see them any more. I am still using the cvsync version of tailor, because I have some very large projects, and I haven't had the time to try to upgrade. The clunkiness is in the CVS sticky tag being set for new files (which I understand has been addressed by TailorOne), and in patch muddiness when multiple patches are applied to the same file during a single sync (which has a bug already in Trac). The tailor repository is a hybrid that sits between two sources to sync. In my case I have a CVS repository on one side, and a darcs repository on the other. For me, tailor is a handy way to remember where I left off sync'ing, and for generating the appropriate cvs and darcs commands. When pulling from darcs, the CVS part of the hybrid realizes there have been changes, and the correct cvs commands are run to commit the change back to the CVS master. When pulling from CVS, the darcs part of the hybrid realizes there have been changes, and the correct darcs commands are run to record the change and push to the darcs master. There are problems when pulling multiple changesets from CVS which originated in darcs. The first CVS changeset modifies the hybrid so that it matches what darcs had several patches back. Then darcs sees there are changes from the current version and a new patch is recorded. This should not occur, as the original patch came from darcs in the first place, and the patch reverts subsequent patches. Then strange dependencies develop, and the darcs repository starts filling up with patches with similar names, but which record very different changes. One solution to this problem is to only pull one patch from darcs at a time, commit to CVS, pull back from CVS, darcs sees no changes, pull next patch from darcs, and so forth. This is what I currently do by hand. Having tailor do this would be nice. If tailor can do it, I believe sync'ing can be done automatically, on a cron or some such. -kolibrie _______________________________________________ Tailor mailing list [email protected] http://lists.zooko.com/mailman/listinfo/tailor
