Subversion problems

[Stephan Kulow]

Am Thursday 17 February 2005 13:10 schrieb Stephan Kulow:
> Because one month is a forseeable time that we can live for without scripty,
> but surely not a full release cycle.
I think I know how we can combine both. I think I could hack cvs2svn to only
create an incremental diff against the last imported revision. This would mean,
we could import all of cvs into svn but mark it read only, then mark some of cvs
read only and after the next incremental update, the svn paths for that cvs modules
are open and at the same time we could e.g. switch anoncvs to anonsvn (taking
longer update cycles for that service though).

But this had some limits though: we could do only svn commits that are not touching
paths were still cvs commits happen. E.g. no cleanup in /branches - and we might
not be able to create new tags/new branches in cvs. As this is no versioned action
in cvs there is no way I see we can handle this reliable.

And of course even this is no long term solution, so we should still make the migration
as soon as possible - I won't implement a two way solution for scripty.

Greetings, Stephan