There are disadvantages. It makes merging between projects a real pita.
I recommend using branches within the same repository. We tried
different repositories for different projects and it has not been fun
trying to get changes from one repository into another.
I concur with Nicolas, don't attach any meaning to the number. If you
want a revision number per project perhaps you should experiment with
svn props and hook scripts....
From: Donkers, H.C. (Kurt) [mailto:K.Donkers@bergson.nl]
Sent: Friday, March 16, 2007 1:34 AM
To: Ryan Schmidt; Nicolas CHARLOT
Subject: RE: Re: One repository / Many projects : How to differenciate
On Mar 13, 2007, at 03:12, Nicolas CHARLOT wrote:
>> At a same time, we are working on many projects. We've setup a
>> repository and want to use it to handle all our projects. The
>> recommended structure is to create a root folder for each project.
>> That's OK. The issue is that we have a global counter for the
>> repository. Is Subversion able to manage revisions by folder ?
>> If not, what do U advise me ?
>No. The revision number is global for the repository.
>My advice to you is not to worry about it. Do not attach any meaning
>to the number, other than "the number of changes that have been made
>in the repository." See also the FAQ:
There is of course also the possibility to use multiple repositories
(one per project), in which case you would have one revision number per
There aren't any major disadvantages to this right?
Received on Fri Mar 16 19:56:52 2007