Fergus Slorach writes:
> On 05/28/2012 09:06 PM, Philip Martin wrote:
>> Fergus Slorach writes:
>>
>>> If a directory containing svn:needs-lock files is copied and
>>> committed, the needs-lock files are left writeable.
>>
>> I think that is correct behaviour.
>
> The problem is that a needs-loc
On 05/28/2012 09:06 PM, Philip Martin wrote:
Fergus Slorach writes:
If a directory containing svn:needs-lock files is copied and
committed, the needs-lock files are left writeable.
I think that is correct behaviour.
The problem is that a needs-lock file should not be writeable without
bei
Fergus Slorach writes:
> If a directory containing svn:needs-lock files is copied and
> committed, the needs-lock files are left writeable.
I think that is correct behaviour.
> The writeable state can be resolved by running 'svn revert' on
> the files, even though the status indicates there is
ergus
On 05/27/2012 10:53 AM, Bert Huijben wrote:
-Original Message-
From: Fergus Slorach [mailto:sug...@gmail.com]
Sent: zaterdag 26 mei 2012 23:57
To: dev@subversion.apache.org
Subject: File permissions are incorrect after directory copy in 1.7
In Subversion 1.7.5:
If a dire
> -Original Message-
> From: Fergus Slorach [mailto:sug...@gmail.com]
> Sent: zaterdag 26 mei 2012 23:57
> To: dev@subversion.apache.org
> Subject: File permissions are incorrect after directory copy in 1.7
>
> In Subversion 1.7.5:
>
> If a directory contain
In Subversion 1.7.5:
If a directory containing svn:needs-lock files is copied and
committed, the needs-lock files are left writeable.
The writeable state can be resolved by running 'svn revert' on
the files, even though the status indicates there is nothing to
revert.
Recipe and run-through res
6 matches
Mail list logo