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
Hi Bert,
Yes, the same recipe in 1.6.17 results in read-only files without the revert.
Actually, in that version, the files are read-only before the commit, which
isn't the desired behavior either - this thread seems to be related:
http://svn.haxx.se/users/archive-2010-10/0228.shtml
fergus
> -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 containing svn:needs-lock files is c
5 matches
Mail list logo