>
> On May 16, 2005, at 5:03 AM, Dave Proctor wrote:
>
>>
>> It seems that if I have a file which has the svn:needs-lock
>> property set,
>> but currently noone has taken the lock, if I alter my working copy
>> of that
>> file, and then just do a svn commit,
>>
>
> If the svn:needs-lock property is set, then the file should be read-
> only. Did your editing tools not notice this?
>
> The point of the read-only-ness is to remind you, "hey, you should
> lock this thing before starting work on it."
>
> Granted, some tools will flat-out ignore the read-only-ness. So as
> Peter said, you could install a pre-commit hook which *demands*
> that any incoming file with a svn:needs-lock property be already
> locked. But IMO, that's a bit too late, the damage is already
> done. Even if the hook prevents such a commit, you've already
> (potentially) wasted your time creating unmergeable changes,
> right? Somebody could have already committed a newer version of
> the file while you were working, and now you've got an unmergeable
> set of conflicts.
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 16 16:56:49 2005