[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: File permissions are incorrect after directory copy in 1.7

From: Philip Martin <philip.martin_at_wandisco.com>
Date: Mon, 28 May 2012 12:33:56 +0100

Fergus Slorach <sugref_at_gmail.com> writes:

> On 05/28/2012 09:06 PM, Philip Martin wrote:
>> Fergus Slorach<sugref_at_gmail.com> 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
> being locked.

Sorry, I misread your report and fixed a different bug. The bug I fixed
was that revert before commit made the file read-only, and it should
remain writetable since the copied file cannot be locked until it has
been committed.

There is still a commit bug: an svn:needs-lock file in a copied
directory should become read-only on commit. I've raised 4188:
http://subversion.tigris.org/issues/show_bug.cgi?id=4188

-- 
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com
Received on 2012-05-28 13:34:36 CEST

This is an archived mail posted to the Subversion Dev mailing list.