Reedick, Andrew wrote:
>
>> Being
>> 'mergable' or not is really an inherent property of the file type, not
>> something dictated by the VC so you probably want to get a lock any
>> time
>> you plan to touch such files whether anyone else remembered to set the
>> property in the VC or not.
>
>
> True, but in such a case, the lock is useless, where useless == not
> guaranteed:
> 1) I checkout the file on Monday,
> 2) you lock the file on Tuesday, and
> 3) I try to check-in on Wednesday...
> 4) I break your lock because I'll be damned if I'm going wait
> for you to finish, and then re-do two day's worth of work.
>
> Unless svn:needs-lock is there from the start, there's no guarantee that
> someone else isn't already working on the file, and there's no guarantee
> he'll ever find out about your lock until it's too late.
If having svn:needs-lock set really provided that guarantee, this thread
wouldn't have started.
I'm just not convinced that this mythical "other person" or his tools
will be any more observant of a needs-lock status than you are unless he
understands the 'guarantee' consists only of your your willingness to
cooperate. If you both work at once, one of you is going to lose
regardless of how much the tool tries to help.
--
Les Mikesell
lesmikesell_at_gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-03-05 00:11:44 CET