Should cvs2svn try to collect changesets at all?
From: Jason Molenda <jason-svn_at_molenda.com>
Date: 2001-04-17 18:48:48 CEST
I think this will be a tricky problem to solve. Is it worth solving
Ignoring all the resource issues, the first step is to generate a
2001-04-10T08:15:10 bob ChangeLog,1.832 foo.c,1.3 bar.h,1.18
The scenario I don't think is solvable -
user bob starts his checkin at time T, across four directories,
At T+30sec, user susan checks in a file in directory C.
At T+45sec, user bob gets to C, finds that his directory is not up to date,
I don't see how you can handle this scenario. Even detecting it
2001-04-10T08:15:10 bob A/f,1.3 B/e,1.8 C/d,1.4 D/c,1.18
cvs2svn has to notice that the T+30 checkin has an earlier revision
In an attempt to collect individual cvs checkins into groupings,
This is an archived mail posted to the Subversion Dev mailing list.