RE: [TSVN] The svn:needs-lock hint ...

And the point in question is: *will* the server reject the commit if the committer doesn't hold the lock-token? Or *can* the server reject the commit, *if* appriopriate hook scripts have been set up?
 
cheers,
 
--Tim
 
(apologies for top-posting)

________________________________

Van: Simon Large [mailto:slarge@slarge.plus.com]
Verzonden: do 21-4-2005 14:12
Aan: dev@tortoisesvn.tigris.org
Onderwerp: Re: [TSVN] The svn:needs-lock hint ...

Nicklas Norling wrote:
> Leeuw van der, Tim wrote:
>
>> "svn:needs-lock\n
>> If this property is set, the file will be made read-only for all
>> users to indicate that a lock has to be acquired before the file can
>> be edited.\n
>>
>>
> Is it really "has to" here? I'm under the impression svn docs said
> *should*. Wasn't *has* left up to
> the repo admin via hook scripts?

The read-only-ness is really just a hint to the user that the file
should not be edited. Anyone can change that flag locally and edit away.
The enforceable part is on the server which can reject any commit
attempt for a file with svn:needs-lock and no lock acquired.

Simon

--
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org