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

RE: Thanks and a global versioning question; WAS:: Help: XML Pars er error, Date Conversion failed

From: Crucius, Wesley <WCrucius_at_sandc.com>
Date: 2004-03-23 21:35:03 CET

Ahh, I think I missed that point. I thought I'd still end up with a global
revision number for respositories served up in this fashion, but I can see
now why that doesn't have to be the case. Am I still correct that multiple
repositories served up this way complicates administration and
breaks/prevents the "External Definitions" and "Vendor Branches" mechanisms
between these repositories?

I have been reading the documentation, and although it is quite good, it's
not all sinking in the first time... I really appreciate your assistance
and patience!

Wes

-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: Tuesday, March 23, 2004 2:20 PM
To: Crucius, Wesley
Cc: 'users@subversion.tigris.org'; 'Tom Vergote'
Subject: RE: Thanks and a global versioning question; WAS:: Help: XML Pars
er e rror, Date Conversion failed

On Tue, 2004-03-23 at 14:13, Crucius, Wesley wrote:
> Also, if using svnserve, it's not possible to run multiple
> repositories (instances of svnserve) on a single server, is it?

Of cours it is. A single svnserve running as a daemon ('svnserve -d') can
serve any number of repositories. The client provides the absolute path to
the repository in the URL.... svn://abs/path/to/repos. Or, if you want to
restrict that, run 'svnserve -d -r /usr/repos', and then all client url's
will be assumed to be relative to '/usr/repos'.

This is all documented in chapter 6.

---------------------------------------------------------------------
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:36:05 2004

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