On 18.11.2011 17:14, Stefan Sperling wrote:
On Thu, Nov 17, 2011 at 03:01:21PM +0100, Stefan Sperling wrote:
I can see your point but I don't think it's a very important issue.
If someone else wants to put in the effort into fixing this in mod_dav_svn
I won't object as long as the feature is pro
On Thu, Nov 17, 2011 at 03:01:21PM +0100, Stefan Sperling wrote:
> I can see your point but I don't think it's a very important issue.
> If someone else wants to put in the effort into fixing this in mod_dav_svn
> I won't object as long as the feature is properly implemented so people
> don't shoot
On Nov 17, 2011, at 07:39, Sergey Skvortsov wrote:
> Do you really believe that normal admin is not smart enough to read docs?
Based on years of answering questions on this list: yes, sometimes. :)
Philip Martin writes:
> I don't understand the "provided ..." bit. It seems to be flat out
> wrong.
Don't take that the wrong way: "It" refers to the code.
--
Philip
Stefan Sperling writes:
> I agree that special-casing the root_dir seems unnecessary even in the
> mirroring case, provided that nested Locations are supposed to work.
I don't understand the "provided ..." bit. It seems to be flat out
wrong. If I fix the line then nested mirroring works when u
On Thu, Nov 17, 2011 at 02:37:36PM +, Philip Martin wrote:
> The order of parent and child in Subversion's INHERIT_VALUE macro only
> has an effect when nesting one Subversion location in another. When not
> nested the parent root_dir is NULL and the child value will be used
> whatever the ord
Stefan Sperling writes:
> Yes, of course it works with SVNParentPath. But I suspect that is
> a result of implementation rather than concious design.
Perhaps, but the line that stops it working looks like an outright bug.
newconf->root_dir = INHERIT_VALUE(child, parent, root_dir);
The orde
On Thu, Nov 17, 2011 at 05:39:37PM +0400, Sergey Skvortsov wrote:
> For example, our practice of layout organizing (simplified example):
>
> /svn
> /devops
> /infra
> /src
> /personal
> /user1
> /user2
> /project
> /prj1
> /prj2
>
On 17.11.2011 16:44, Stefan Sperling wrote:
On Thu, Nov 17, 2011 at 11:50:20AM +, Philip Martin wrote:
Stefan Sperling writes:
How do we avoid ambiguity when handling requests to nested Locations?
How can a client access a folder /bar inside a repository at Location /svn
if another reposi
On Thu, Nov 17, 2011 at 11:50:20AM +, Philip Martin wrote:
> Stefan Sperling writes:
>
> > How do we avoid ambiguity when handling requests to nested Locations?
> > How can a client access a folder /bar inside a repository at Location /svn
> > if another repository exists at a nested Location
Stefan Sperling writes:
> How do we avoid ambiguity when handling requests to nested Locations?
> How can a client access a folder /bar inside a repository at Location /svn
> if another repository exists at a nested Location /svn/bar?
Yes, I was surprised too! If we assume that /svn and /svn/fo
On Thu, Nov 17, 2011 at 11:01:39AM +, Philip Martin wrote:
> [Adding dev]
>
> Philip Martin writes:
>
> > Sergey Skvortsov writes:
> >
> >> Also, in 1.7 reading repos is working fine:
> >>
> >> "OPTIONS /svn/foo/bar HTTP/1.1" 200
> >> "REPORT /svn/foo/bar/!svn/me HTTP/1.1" 200
> >>
> >> bu
Philip Martin writes:
> [Adding dev]
Gah! Got the address wrong. I'll start a thread on dev.
--
Philip
[Adding dev]
Philip Martin writes:
> Sergey Skvortsov writes:
>
>> Also, in 1.7 reading repos is working fine:
>>
>> "OPTIONS /svn/foo/bar HTTP/1.1" 200
>> "REPORT /svn/foo/bar/!svn/me HTTP/1.1" 200
>>
>> but only POST fails:
>> "POST /svn/foo/bar/!svn/me HTTP/1.1" 500
>>
>> So the problem is
Sergey Skvortsov writes:
> Also, in 1.7 reading repos is working fine:
>
> "OPTIONS /svn/foo/bar HTTP/1.1" 200
> "REPORT /svn/foo/bar/!svn/me HTTP/1.1" 200
>
> but only POST fails:
> "POST /svn/foo/bar/!svn/me HTTP/1.1" 500
>
> So the problem is not in Apache or configuration but in mod_dav_svn
On 17.11.2011 11:35, Cooke, Mark wrote:
-Original Message-
From: Sergey Skvortsov [mailto:s...@protey.ru]
Sent: 17 November 2011 07:09
Subject: Re: "svn commit" does not work with SVNParentPath in
location and 1.7-client (HTTPv2)
I disagree. This cite is irrelevant t
On 17.11.2011 11:40, David Chapman wrote:
On 11/16/2011 11:08 PM, Sergey Skvortsov wrote:
On 16.11.2011 19:56, Stefan Sperling wrote:
On Wed, Nov 16, 2011 at 06:37:39PM +0400, Sergey Skvortsov wrote:
s/"svn update"/"svn commit"/
On 16.11.2011 18:31, Stefan Sperling wrote:
On Wed, Nov 16, 201
On 11/16/2011 11:08 PM, Sergey Skvortsov wrote:
On 16.11.2011 19:56, Stefan Sperling wrote:
On Wed, Nov 16, 2011 at 06:37:39PM +0400, Sergey Skvortsov wrote:
s/"svn update"/"svn commit"/
On 16.11.2011 18:31, Stefan Sperling wrote:
On Wed, Nov 16, 2011 at 02:43:17PM +0400, Sergey Skvortsov wro
> -Original Message-
> From: Sergey Skvortsov [mailto:s...@protey.ru]
> Sent: 17 November 2011 07:09
> Subject: Re: "svn commit" does not work with SVNParentPath in
> location and 1.7-client (HTTPv2)
>
> I disagree. This cite is irrelevant to my
On 16.11.2011 19:56, Stefan Sperling wrote:
On Wed, Nov 16, 2011 at 06:37:39PM +0400, Sergey Skvortsov wrote:
s/"svn update"/"svn commit"/
On 16.11.2011 18:31, Stefan Sperling wrote:
On Wed, Nov 16, 2011 at 02:43:17PM +0400, Sergey Skvortsov wrote:
Configuration for Apache:
DAV svn
On Wed, Nov 16, 2011 at 06:37:39PM +0400, Sergey Skvortsov wrote:
> s/"svn update"/"svn commit"/
>
> On 16.11.2011 18:31, Stefan Sperling wrote:
> >On Wed, Nov 16, 2011 at 02:43:17PM +0400, Sergey Skvortsov wrote:
> >>Configuration for Apache:
> >>
> >>
> >> DAV svn
> >> SVNParentP
s/"svn update"/"svn commit"/
On 16.11.2011 18:31, Stefan Sperling wrote:
On Wed, Nov 16, 2011 at 02:43:17PM +0400, Sergey Skvortsov wrote:
Configuration for Apache:
DAV svn
SVNParentPath /usr/home/svn
SVNListParentPath on
DAV svn
SVNParentPath /u
22 matches
Mail list logo
