File Locking

[Arne Babenhauserheide]

Am Donnerstag 16 Oktober 2008 17:52:09 schrieb Arne Babenhauserheide:
> And the "disallow saving the modified state" aspect is an inherently flawed
> idea, since it poses unnecessary restrictions on the individual developer
> even though his actions don't affect others if he doesn't publicize his
> changes.

Damn, this is typical. I speak strongly against something and now I see a 
usecase :) 

File locking on commit could be useful if there are reference files which 
might be changed by automatic tools. 

To avoid overwriting the reference files by accident developers might want to 
use a Mercurial extension which recognizes "soft locked" files and asks if the 
developer really wants to do a commit which changes them, of if he wants to 
exclude them. 

Naturally teh dev could just disable the warning by disabling the extension, 
but the feature might be useful to avoid having to change your personal 
history afterwards because you accidently modified a reference file in one of 
your commits. 

Best wishes, 
Arne
-- 
-- My stuff: http://draketo.de - stories, songs, poems, programs and stuff :)
-- Infinite Hands: http://infinite-hands.draketo.de - singing a part of the 
history of free software.
-- Ein Würfel System: http://1w6.org - einfach saubere (Rollenspiel-) Regeln.

-- PGP/GnuPG: http://draketo.de/inhalt/ich/pubkey.txt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://selenic.com/pipermail/mercurial/attachments/20081016/e263457d/attachment.pgp