Lalo Martins wrote: >An now on to Tailor: > >Tailor is a tool originally written to sync SVN (or was it CVS?) >repositories to Darcs. It's now a very interesting cross-VC syncer. I >helped Rednaxela set up a Tailor config to mirror crossfire's cvs repo to >bzr (with the intention of using the bzr version myself, too, once it was >working). I just thought I should mention. Whatever distributed VC we >switch to, tailor could be used to do the migration. I'd be willing to do >the actual work (well, what little there is, as Rednaxela already did the >ugly parts). And it can also be used afterwards, to keep a read-only CVS >copy of the main branch, as you say. > Well, yes, not much to do to get that working, I pretty much made a script that deals with all of it. There is however one issue. I didn't get syncing back to SF cvs (i.e. two way sync. I was trying to at the time hack some stuff together so I could have distributed VC features with the existing CVS server) isn't quite working, however syncing back to a CLEAN cvs repository for read-only cvs purposes should work perfectly well. Or in other words, when keeping a read-only cvs copy of the main branch, we likely couldn't overwrite the existing SF CVS module and would instead have to make a new module on cvs for it Another note for those who don't know much about tailor, it DOES preserve revision history very nicely.
Alex Schultz Alex Schultz _______________________________________________ crossfire mailing list [email protected] http://mailman.metalforge.org/mailman/listinfo/crossfire
