Re: mod_dav_dvn+SVNParentPath with non-repo subdirs

2019-09-22 Thread Thorsten Schöning
Guten Tag Branko Čibej, am Samstag, 21. September 2019 um 19:53 schrieben Sie: > Basically it's as likely as someone contributing a patch for that. Note > that this may not be trivial due to backwards-compatibility concerns, > not only about how repositories are found on disk but also (as Daniel >

Re: mod_dav_dvn+SVNParentPath with non-repo subdirs

2019-09-21 Thread Branko Čibej
On 11.06.2019 20:15, Thorsten Schöning wrote: > Hi all, > > I'm hosting SVN-repos using svnserve and by providing the argument > "--root" with the parent dir of all my repos. In the past, all repos > have been placed as a direct child of the given path, but recently I > refactored that to manage re

Re: mod_dav_dvn+SVNParentPath with non-repo subdirs

2019-09-21 Thread Daniel Shahaf
Thorsten Schöning wrote on Tue, Jun 11, 2019 at 20:15:45 +0200: > So, is there a reason why mod_dav_svn doesn't support additional > subdirs? Is that likely to be changed? I can't think of a reason against adding that. > Is it likely that svnserve will stop supporting addiitonal child dirs? No.

Re: mod_dav_dvn+SVNParentPath with non-repo subdirs

2019-09-21 Thread Thorsten Schöning
Guten Tag Doug Robinson, am Montag, 12. August 2019 um 23:38 schrieben Sie: > It works as you'd expect so you should only require one SVNParentPath > directive assuming that all of your repositories are within that single > tree. Just read this today. Are your sure svnadmin and mod_dav_svn behave

Re: mod_dav_dvn+SVNParentPath with non-repo subdirs

2019-08-12 Thread Doug Robinson
Thorsten: It works as you'd expect so you should only require one SVNParentPath directive assuming that all of your repositories are within that single tree. I suspect the wording needs a bit of a revamp. Cheers. Doug On Tue, Jun 11, 2019 at 2:15 PM Thorsten Schöning wrote: > Hi all, > > I'm

mod_dav_dvn+SVNParentPath with non-repo subdirs

2019-06-11 Thread Thorsten Schöning
Hi all, I'm hosting SVN-repos using svnserve and by providing the argument "--root" with the parent dir of all my repos. In the past, all repos have been placed as a direct child of the given path, but recently I refactored that to manage repos by customers, topics and stuff. This works pretty eas