On Wed, 2005-02-02 at 16:00, Mark Phippard wrote:
> "Brian W. Fitzpatrick" <fitz@collab.net> wrote on 02/02/2005 04:53:37 PM:
>
> [snip]
>
> > Propset:
> > - Setting the svn:needs-lock property sets the file to read-only
> > (It also canonicalizes the value to '*')
>
> Before setting the file to read-only, shouldn't it check to see if it is
> locally modified?
Hmm. I'm not sure about that--if the prop is set, and the user has
local mods, isn't it safe to assume that the user is doing it
intentionally?
> You do not mention unlock. But I would assume if you run a command that
> unlocks a file with this property set, whether it be the unlock or commit
> command, that it would set the file to read-only?
Doh. Of course I skipped the obvious. Here's the update list of
behaviors (I've not included commit as that will call unlock):
svn:needs-lock behaviors:
=========================
Checkout:
- If svn:needs-lock is set on a file when the file is checked out, set
the file to read-only.
Update:
- If svn:needs-lock is unset in wc, but update sets it: Set file to
read-only.
- If svn:needs-lock is set in wc, but update unsets it: Set file to
read-write.
- If svn:needs-lock is set or unset in both places: Do nothing.
Propset:
- Setting the svn:needs-lock property sets the file to read-only
(It also canonicalizes the value to '*')
Propdel:
- Removing svn:needs-lock sets the file to read-write.
Propedit:
- If the property is changed via propedit, we need to canonicalize it
to '*'.
Lock:
- If svn:needs-lock is set, the file is set to read-write.
Unlock:
- If svn:needs-lock is set, the file is set to read-only.
-Fitz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Feb 2 23:06:56 2005