convert-repo and an interesting unhandled CVS oddity

[Eric Hopper]

In CVS, branches can be mentioned out of topological sort order, even though
changes cannot be.  This is because a branch changes a repository in a way
that does not show up as a changeset.

This means that convert-repo's technique of checking in changes as it scans
the repository may fail on some repositories as when an ancestor branch is
mentioned it might be that no changes have been checked in on that ancestor
branch, and therefor it's never been mentioned as a branch.  I, in fact,
have a repository in which this is the case right now.

I might be trying to fix this at some point, possibly by having a pre-scan
that builds up a mapping of CVS change # to branch base.  I've considered a
different technique in which CVS changes sometimes get checked in out of
order, but I think that will be way too complicated.

Just thought I'd mention,
-- 
Eric Hopper -- http://www.omnifarious.org/~hopper/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial-devel/attachments/20070516/a6d1b4f8/attachment.html>