#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]):
The problem seems to be the sort() call in ChangeSetCollector.__iter__,
which sorts on (timestamp, author, changelog).
To correct the problem, the sort algorithm would need to be updated. This
could be done using a topological sort based on the following partial
order: if a changeset creates revision X for a given file, it must come
after changesets with lower revision numbers for that file. If there is
ambiguity, the changeset timestamp can be used as a tie breaker.
Alternatively, the problem can be detected by sorting the changesets as is
done right now, and then check for cases where the revision numbers are
not increasing as you go through the changesets.
--
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
