On Fri, Apr 23, 2010 at 12: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?
Check for Modifications -> Check Repository will show any items locked
in the repository location corresponding to your WC.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2593643
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-04-23 18:26:46 CEST