#37: problems converting cvs -> bzr in presence of bad non-ascending dates
---------------------------------+------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: lele
Type: defect | Status: new
Priority: major | Milestone: VersionOne
Component: cvs | Version: 0.9
Resolution: | Keywords:
---------------------------------+------------------------------------------
Comment (by [EMAIL PROTECTED]):
Here's a viewcvs URL showing the date screwup.
http://cvs.gnome.org/viewcvs/jhbuild/modulesets/gnome24.modules?view=log&logsort=cvs#rev1.60
rev 1.59 - 2003-09-09
rev 1.60 - 1997-01-04
rev 1.61 - 1997-01-04
rev 1.62 - 2003-09-12
Tailor seemed to correctly break the CVS history into changesets (even
though the dates aren't sequential, the changes in each changeset still
share the commit date).
On my initial run (before editing the RCS files to correct the dates), the
problems I saw were:
* the first of these 1997 changsets were picked as revision 1
* Tailor bombed out part way through, when it tried to tell bzr to delete
a file that it didn't know about (I assume that it skipped the changeset
where the file originally got added).
After correcting the dates in the RCS files, the conversion process went
off without a hitch.
It would be nice if Tailor could either support bad CVS history like this,
or error out early when this condition is encountered.
--
Ticket URL: <http://progetti.arstecnica.it/tailor/ticket/37>
Tailor <http://www.darcs.net/DarcsWiki/Tailor>
An inter-VCs changeset exchanger
_______________________________________________
Tailor mailing list
[email protected]
http://lists.zooko.com/mailman/listinfo/tailor
