[issue1610] CVS conversion: branches are in arbitrary, unpredictable order

[Greg Ward]

New submission from Greg Ward <greg-hg at gerg.ca>:

When converting from CVS, branches are in arbitrary order that makes no
chronological sense.  For example, converting our large CVS repository at work
results in a Mercurial repository where the "most recent" branch is eight years
old, so tip of the brand-new Mercurial repository dates from 2001.  That just
looks weird.  You have to dig several hundred changesets back in history to find
the head of default or any of our currently active release branches.

It looks like branches are simply in hash order from self.lastbranch in cvs.py.
 I *thought* that this would fix it:

--- a/hgext/convert/cvs.py
+++ b/hgext/convert/cvs.py
@@ -172,6 +172,7 @@
                         continue
 
             self.heads = self.lastbranch.values()
+            self.heads.sort()
         finally:
             os.chdir(d)

... but that does not appear to suffice.  Hmmmm.  Will investigate more tomorrow.

----------
assignedto: gward
messages: 9096
nosy: gward
priority: bug
status: unread
title: CVS conversion: branches are in arbitrary, unpredictable order
topic: convert

____________________________________________________
Mercurial issue tracker <mercurial-bugs at selenic.com>
<http://www.selenic.com/mercurial/bts/issue1610>
____________________________________________________