Re: [Monotone-devel] Monotone CVS sync

[Christof Petig]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

William Uther schrieb:
>> State:
>> - - cvssync1: finished, tested, slow
>> - - cvssync3: work in progress, did work before the summit, needs a bit
>> more work to compile again, passes test cases but I saw some strange
>> issues
>> - - cvssync4: proposed by Nathaniel, still to get properly designed
> 
> How do these map to the source code/branches?  How do I know which I'm
> using?  e.g. grep for cvssync1 doesn't match anything in the source.

cvssync1 matches on of the heads of nvm.cvssync. There is an upgrade
path which I used.

> Does the fact that cvssync3 "did work before the summit" mean that my
> reverting to a revision from the end of January means I might have a
> working cvssync3?

yes, that should work somewhat (it's not well tested).

> Are these different sync mechanisms going to be compatible?  Will there
> be an upgrade path?  e.g. if I start using cvssync3 and then you get
> cvssync4 going, am I going to be able to keep syncing?
> The way things stand, mtn ends up with a complete history, and CVS ends
> up with a limited history.  That is fine, but if the update means
> throwing out the mtn db and re-pulling from CVS then I'd lose history
> (which may not be the end of the world, but...).  If the update means
> changing the CVS repository, that is more problematic.

Usually I preserve my monotone history during upgrades of cvssync. A
future version of cvssync will maintain compatibility or provide an
upgrade path.

> One final question... what should cvssync do with moves and renames?  It
> seems to break things at the moment.   It isn't clear what should
> happen...  is it best to do a grep for "Renamed entries:" in the log and
> call for help if it matches?  Then the user manually disapproves of that
> revision and things work again?

renames map to deletion and creation - as usual within CVS projects. You
loose the history of the file.

   Christof

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFF1ihrng+R+0ucfO0RAtWDAKC2L5LmzwNA7Uyc72CX4dKFXSeokgCfb4JE
WcnHfzvmLlBS32Sw/T0cNLM=
=X6Pr
-----END PGP SIGNATURE-----