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

Re: [TSVN] What to see immediately?

From: SteveKing <stefankueng_at_gmail.com>
Date: 2005-04-19 11:20:49 CEST

2005/4/19, Molle Bestefich <molle.bestefich@gmail.com>:
> Bill.Hughes@cgi-europe.com wrote:
> > Given the comments in other messages that SVN doesn't actually enforce locks
> > if you manually change a files read-only status perhaps tsvn should check
> > for this too, until svn does implement it.
>
> It's easily enforceable on the server side with a pre-commit hook that does:
> 1. Does file <x> have svn:needs-lock set?
> 2. If yes, does the commiting user have the appropriate lock?
> 3. If not, reject the commit.
>
> I think that anybody working with locking would implement a hook of
> the above sort.

Why implement? I just would use that one ;)
https://svn.collab.net/repos/svn/trunk/contrib/hook-scripts/pre-lock-require-needs-lock.py

Stefan

-- 
       ___
  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
Received on Tue Apr 19 11:22:47 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.