From: Martin Langhoff <martin.langhoff@gmail.com>
Date: Tue, 12 Jan 2010 19:33:18 GMT
Subject: Re: Interest in locking mechanism?
Message-ID: <46a038f91001121133r62b3d748n38ca27234f18e960@mail.gmail.com>
In-Reply-To: <32541b131001121124u541de280na9184183d8704dc8@mail.gmail.com>

On Tue, Jan 12, 2010 at 8:24 PM, Avery Pennarun <apenwarr@gmail.com> wrote:
> really).  Just make a 'co' command that writes your username to
> .filename.lock and chmods the file; then write a ci command that
> checks the lockfile to make sure it's yours, deletes the lock file,
> git commits it, and chmods the file back again.

Actually -- on the same track but even better: if you are using a
unixy system, you are likely to have all the users belong to a group,
and the files are editable by the group because they are rwx by group
members.

So write your own "git-lock" command that does "chmod g-w $@";
git-unlock reenables the group-writable bit. Done.

For more arcane things, use ACLs. On Windows I am sure there is a
commandline tool to touch ACL bits.

hth,



m
-- 
 martin.langhoff@gmail.com
 martin@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff