#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:
---------------------------------+------------------------------------------
Changes (by Lele Gaifax):
* component: tailor => cvs
Comment:
Uhm, surely tailor cannot be a panacea for every shortcoming of cvs, even
if it's just great if it can reduce those at a minimum.
Anyway, I cannot see how tailor could reorder and reset the date: there's
a chicken and egg situation, where tailor uses the timestamp of changes to
group them in a single changeset, so the order is fundamental just to get
at them.
But what's the problem? Was tailor unable to bootstrap the project, or
what? Could you attach the log, or a better description of the issue?
--
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
