Well, at least I'm not [completely] crazy... Although, I don't like the
fact that I'd have to maintain/administer multiple repositories and that it
would break the "External Definitions" and "Vendor Branches" capabilities, I
think... Also, if using svnserve, it's not possible to run multiple
repositories (instances of svnserve) on a single server, is it? Well, unless
I bind each instance to a different port number, which seems hokey. It's
cerainly not a show stopper for me if I have to run Apache, but setting up
svnserve certainly is simple in comparison. Am I correct to assume that
using Apache would make it possible to have multiple repositories without
having apache listening on multiple ports?
Wes
-----Original Message-----
From: Tom Vergote [mailto:tom@tomvergote.be]
Sent: Tuesday, March 23, 2004 2:02 PM
To:
Subject: Re: Thanks and a global versioning question; WAS:: Help: XML Parser
e rror, Date Conversion failed
On Tue, 2004-03-23 at 20:26, Crucius, Wesley wrote:
> [snip]
> My proposed users aren't going to like (or
> understand) the global revision number
I'm facing the same problem and that's why i'm considering a repository per
project, "the project gets a new revision every time someone commits" seems
easier than "something in the repository got committed so everything has a
new revision now, and thats why that project jumped to rev 317 even though
it's still only a html design"
> [snip]
> Any thoughts?
>
> Thanks again,
> Wes Crucius
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 23 21:14:14 2004