Question

My company is performing a SVN repository migration and I would like to avoid overlapping of revision numbers between the two repositories (which are both active at the time being).

My requirement is to force the revision of the new repository to a specific revision number (say: 100.000).

By analyzing the FSFS repository I have come across the “db/current” file which sounds like the right place where to change the repository number.

Does anyone have any experience with this procedure? I would like to avoid strange things happening in the future!

PS: I understand I can create “100.000” dummy commits to the repository. Please share your experience with such procedure and possible performance issues of the repository during and after the prodecure

PS3: I understand that it might be a good idea to have everybody commit working copies before the procedure. This is not a problem for us (the new repository has very limited users right now). Still, if you have experience with this or similar requirements, please share! 🙂

PS3: I understand this is not a standard SVN procedure and many might object with the requirement itself. Let’s just assume my requirement is sound! 🙂

Answer 1

http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=940194 :

Q: Is there a way to artificially increment the repository revision
number in subversion?

A: The only way to do it would be to commit a number of dummy revisions.