Re: Show colleagues locks BEFORE edit...

On 23 April 2010 17:16, Dan <dan.aves_at_blackrock.com> wrote:
> I appreciate that "Locking" doesnt fit easily with the subversion ethos, but there's one standout feature that would really complete the tool for me:
>
> Showing other people's locks when updating my local source.
>
> This is primarily for the purposes of forcing developers not to START making changes to specific files if they are being modified (i.e. important base objects &/or utilities).
>
> At present, I can't see how to do this nicely - my colleagues can happily modify key base classes & only notice the lock when they want to commit - at which point they may have wasted time & effort already - I really want them to see a lock warning if they try to modify.
>
> I'm happy with the general modify-commit-merge mechanism for 99% of my source, but it's just not convenient for certain key files, IF they are being modified.
>
> Have I missed something?

If the svn:needs-lock property is set on a file, that file is made
read-only unless you have explicitly obtained a lock on it. For those
key files which don't merge well you should set that property so that
a developer has to get a lock before editing (assuming the editor will
warn you that the file is read-only and not wait until you try to save
before telling you).

Simon

-- 
:       ___
:  oo  // \\      "De Chelonian Mobile"
: (_,\/ \_/ \     TortoiseSVN
:   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
:   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2593847
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].