Locking
From: Moore, Tom <Tom.Moore_at_aig.com>
Date: 2007-11-13 17:43:51 CET
Lets say we have a scenario where file changes can't be merged, such as
User A locks car.jpg and proceeds to work on the image
User B does a svn update to update their working copy in order to work
If the svn:needs-lock property is attached to car.jpg, then User B has a
A worse case scenario is that the svn:needs-lock property was never set.
Why is the lock information so obscure?
If I have done an update, then locally then the working copy knows that
O 11 car.jpg
That O means its locked by other. User B then has to run svn info
Since the knowledge that the file is locked was passed to the working
Ok, so sometimes the logs are long and we can miss this information.
If the user is not disciplined, or just missed the output from the
Commit of car.jpg failed as car.jpg is currently locked by User: User A
Lastly, I think that svn status -u car.jpg should not only indicate that
Is there agreement on my statements, or am I barking up the wrong source
Tom
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.