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

Re: Feature suggestion: update/lock and unlock/commit

From: Rainer Müller <mueller_rainer_at_gmx.de>
Date: 2005-10-21 16:04:01 CEST

Maciej Miąsik wrote:
> Committing after unlock is just another way of preventing conflicts. It
> doesn't interfere with the unlock after commit option, it sort of
> complements that functionality.

It is dangerous to unlock before committing because another user could lock that
file just after you unlocked it. So your will fail and then both users could two
different (maybe conflicting) versions of this file.
"Unlock after commit" happens automatically since a commit normally unlocks all
committed files if you do not set "Keep Locks".


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

Received on Fri Oct 21 15:13:24 2005

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