subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Evans <>
Subject Revisions not in chronological order
Date Fri, 29 Oct 2010 14:42:26 GMT

My repository is made up of a load of folder loaded from cvs2svn dumps.
These were loaded individually and have overlapping date ranges.
When doing an "svn load" it looks like SVN assigns each commit to the
next revision, regardless of the date the commit occurred.

As a result the rage of revisions created for each of the loads have
overlapping dates and the revisions of the repository are not chronological. 


C:\Windows\system32>svn log -v -r 2000 https://svn/svn/repo/
r2000 | <username> | 2006-07-13 11:41:27 +0100 (Thu, 13 Jul 2006) | 2 lines
Changed paths:
   M /Folder1/file1


C:\Windows\system32>svn log -v -r 20000 https://svn/svn/repo/
r20000 | <username> | 2003-08-19 04:30:07 +0100 (Tue, 19 Aug 2003) | 1 line
Changed paths:
   A /Folder2/file1


C:\Windows\system32>svn log -v -r 21000 https://svn/svn/repo/
r21000 | <username> | 2006-05-19 11:55:33 +0100 (Fri, 19 May 2006) | 1 line
Changed paths:
   A /Folder2/file2


This causes problems for "svn log" and "svn cat" when attempting to get
revisions at a particular date for a folder. SVN will find the lowest numbered
revision for that date, regardless of whether the folder exists for that
revision. e.g.

C:\Windows\system32>svn log -r {2010-07-11} https://svn/svn/repo/Folder3
svn: Unable to find repository location for 'https://svn/svn/repo/Folder3' in revision 63506

However there are revisions for that date...

C:\Windows\system32>svn log -r 114691 https://svn/svn/repo/Folder3
r114691 | <username> | 2010-07-11 11:12:14 +0100 (Sun, 11 Jul 2010) | 2 lines

message 4


I've tried "svndumptool check" to check a dump of the entire repository, but it comes back
An "svn load" of the dump seems to keep the same revision numbers and dates.

Is there a way of reorganising the repository to have all revisions in 
chronological order?
How can I avoid this happening in the future?
Or is there some other way for getting round this?


Gloucester Research Limited believes the information provided herein is reliable. While every
care has been taken to ensure accuracy, the information is furnished to the recipients with
no warranty as to the completeness and accuracy of its contents and on condition that any
errors or omissions shall not be made the basis for any claim, demand or cause for action.
The information in this email is intended only for the named recipient.  If you are not the
intended recipient please notify us immediately and do not copy, distribute or take action
based on this e-mail.
All messages sent to and from this email address will be logged by Gloucester Research Ltd
and are subject to archival storage, monitoring, review and disclosure.
Gloucester Research Limited, 5th Floor, Whittington House, 19-30 Alfred Place, London WC1E
Gloucester Research Limited is a company registered in England and Wales with company number

View raw message