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

Re: Feature / Bug - File lock icon, checking for modifications

From: Jean-Marc van Leerdam <j.m.van.leerdam_at_gmail.com>
Date: 2006-04-26 07:32:42 CEST

Edward,

On 26/04/06, Edward Harvey <eharvey@chilsemi.com> wrote:
> Here's a question for you --
>
> Wouldn't it be ideal to prevent anyone from working on a file, if that
> file is already locked by someone else?

Yes, and that can already be achieved by setting the svn:needs-lock
property!! That causes your local file to become read only until you
acquire the lock. If that doesn't prevent your workers from modifying
the file without thinking about 'why is this file read only?!?' then
IMHO they need some education about working in teams.

As already stated in earlier mails in the curernt thread, this
property can be automatically set on all added files, so it requires
no additional actions for your developers (as soon as the auto-props
are set up).
All they need to do is look at the file, notice the fact that it needs
a lock, right click and do a 'get lock'. Once that is done they can
start working on the file.

--
Regards,
Jean-Marc
----------------
    ___
   // \\  @@     "De Chelonian Mobile"
  / \_/ \/._)    TortoiseSVN
 <\_/_\_/ /      The coolest Interface to (Sub)Version Control
  /_/   \_\      Check out http://tortoisesvn.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: users-help@tortoisesvn.tigris.org
Received on Wed Apr 26 07:32:49 2006

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