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

Re: 'svn cp' disregards svn:needs-lock on Windows

From: Anton Shepelev <anton.txt_at_gmail.com>
Date: Sun, 24 Dec 2017 22:41:58 +0300

Brane to Anton Shepelev:

> > Is it an error or expected behavior that local
> > attribute to the copies of files that have the
> > svn:needs-lock property and are marked as read-
> > only in the woking copy at their original loca-
> > tions?
>
> It's expected. The new file is essentially in a
> 'modified' state, even though it's contents have
> not changed.

Does not this violate the requirement to lock a file
*prior* to modifying it?

> After you commit it, it will become read-only in
> the working copy.

No, it does not. Only after I delete the file and
update it, does SVN "restore" it with the read-only
attribute.

-- 
Please, do not forward replies to my e-mail.
Received on 2017-12-24 20:42:20 CET

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