On Wed, Oct 10, 2012 at 1:39 AM, Kate F <kate_at_elide.org> wrote:
> I have several repositories which I'm currently serving over http.
> Some have their own domain name (http://svn.project.org/), some are
> multiple projects belonging to one company (http://svn.company.com/xyz
> and http://svn.company.com/abc), and others are shared under the same
> I'd like to stop using Apache, and serve these over svn:// instead,
> using svnserve. But I don't want to lump them all together in the same
> URL space. And I don't want to run svnserve lots of times on different
> IPs or ports.
> There's an open ticket with a patch which implements exactly what I'd like:
Yes, that looks good. I just checked the /trunk
code for changes during the last 4 years that
would render the patch incomplete. But it seems
to be still valid (except for the option ID).
> That ticket provides "virtual hosts" for svnserve (in the spirit of
> HTTP's Host: header). The patch looks pretty straightforward; it seems
> that all the information is conveniently present:
> Would somebody be so kind as to commit this, please?
If no-one is opposed to that, I will simply apply
and commit this next weekend.
Join us this October at Subversion Live
for two days of best practice SVN training, networking, live demos,
committer meet and greet, and more! Space is limited, so get signed up
Received on 2012-10-10 17:44:50 CEST