[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Specifying a start revision number for a new repository

From: Ryan Schmidt <subversion-2010d_at_ryandesign.com>
Date: Wed, 1 Dec 2010 06:54:58 -0600

On Dec 1, 2010, at 06:45, benstoever_at_aol.com wrote:

> I'm developing and hosting an open source project
> (treegraph.bioinfweb.info) and want to start using subversion to
> manage the source codes (including a webinterface with sventon).
> Until now the source codes revisions were organized manually without
> any version controol system in formof f backups and the current
> revision is 197. I have already set up a svn server with an empty
> repository and want the revision numbers in svn to start with 198,
> when uploading my source codes there, to avoid having different
> revision numbers in svn and the download section of the website.
> Is there any way to set an initial revision number when doing the
> first import to svn?
> I have not found any information on that, and the only idea I have
> until now is to make 197 more or less senseless commits before
> committing the first real change to my source codes. I would really
> appreciate if anyone known a more elegant (and faster) way of doing
> that.

Creating 197 throwaway revisions is the only thing that occurs to me as well.

However, the revision number is really only "the number of changes that have been made to the repository" so you shouldn't attach too much meaning to it.

If you have kept backups of each (or some) of your existing 197 revisions that you managed by hand, perhaps you'd like to import these into the repository. You could use the svn_load_dirs.pl script to help you with this, assuming each revision is in its own complete directory somewhere. Then your 197 revisions in the repository wouldn't be senseless; they'd be your existing history.
Received on 2010-12-01 13:55:41 CET

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.