> > > I would update from CVS to darcs. Do my work in darcs. When I am ready > > > to commit back to CVS, I tell tailor to sync. Tailor would first check > > > to see if there had been any updates to CVS, and pull those, creating > > > darcs patches for each changeset. Then immediately after committing > > > each darcs patch to CVS, tailor would check to see if there had been any > > > updates to CVS. There would be at least one (from the patch just > > > committed), which would be pulled back. CVS would now be happy, and > > > darcs would detect no changes, and would also be happy. Tailor could > > > then continue with the next darcs patch to commit to CVS.
... > The scenario I describe is not theoretical. That is the process I > manually take to keep my darcs and CVS repositories in sync. I know > that it works, because I use it daily. I see. So when tailor does the "CVS to darcs" pass, if applying the new CVS patch leaves no change (because the change was already performed by the pre-existing darcs patch), then it doesn't create a new patch. I hadn't tried something like that because it seemed weird for some patches to have appeared in darcs world and moved into CVS world and other patches to have appeared in CVS world and moved into darcs world. I had thought that all patches should be funnelled through the same process. However, now that you've brought it to my attention, I can't think of any actual problem that would result. Thank you! Regards, Zooko _______________________________________________ darcs-users mailing list darcs-users@darcs.net http://www.abridgegame.org/mailman/listinfo/darcs-users
