[issue1129] Convert from svn scrambles order of commits slightly
mercurial-bugs at selenic.com
Wed May 21 20:54:28 CDT 2008
New submission from Greg Ward <greg-hg at gerg.ca>:
I'm converting a Subversion repository with 282 revisions dated from 1997-10-01
to 2008-05-19. (It was originally a CVS repository, which is why there are
revisions older than Subversion itself!) When I use "hg convert" on it, hg
correctly creates 282 revisions numbered 0 .. 281. Unexpectedly, though, it
does not maintain chronological order: the most recent revision in svn is r282
from 2008-05-19 17:36:51; that becomes hg revision 279. Revisions 280 and 281
are from a tiny CVS branch created in April 2004 that cvs2svn subsequently
converted as two Subversion revisions.
The upshot is that the highest hg revision number is *not* the most recent
commit, which violates my expectations from reading
http://hgbook.red-bean.com/hgbookch2.html. It also means that my favourite
thing about Subversion (chronologically increasing revision number) does not
carry over to Mercurial, despite the fact that Mercurial also boasts a
chronologically increasing revision number.
I've put a copy of the svn repository here:
I'll attach "svn log" and "hg log" output to illustrate.
I'm using hg 1.0, built with "make local" and running out of the download dir.
(But I saw the same thing with Ubuntu's package mercurial-0.9.5-3 in hardy.)
title: Convert from svn scrambles order of commits slightly
Mercurial issue tracker <mercurial-bugs at selenic.com>
More information about the Mercurial-devel