On 10/13/2006 2:12 PM, Ted Dennison wrote:
> Kevin Greiner wrote:
>> Personally, I prefer creating a single repo since it's easier to
>> administer
>> (backup, verify, dump/load are easier on a single repo) and permisions
>> are
>> now flexible enough to allow fine-grained control. A single repo also
>> means
>> the creation of a new project is very easy. Creating a whole new repo is
>> harder, requiring the intervention of an admin or script on the svn
>> server.
>
> I'm not the expert I need to be to really argue this, but...
>
> Wasn't there recently an argument here for multiple repositories, on the
> basis that working with revisions can get annoying when the entire
> repository (and thus every "project" in it) gets a new revision every
> time something changes?
That sounds like an "annoyance" to a CVS user, but SVN users tend not to
pay too much attention to the revision number. If you want to know how
active a particular project has been, and you think commits are an
accurate measure of that, use svn log to see how many commits there have
been in the path(s) associated with that project, e.g.
svn log -q | grep ^r
Duncan Murdoch
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Oct 13 21:12:58 2006