git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Interest in locking mechanism?

From
Edward Z. Yang <ezyang@mit.edu>
Date
Jan 12, 2010, 19:43 UTC
Message-ID
<1263325308-sup-5516@ezyang>
In-Reply-To
<46a038f91001121133r62b3d748n38ca27234f18e960@mail.gmail.com>
Excerpts from Martin Langhoff's message of Tue Jan 12 14:33:18 -0500 2010:
> So write your own "git-lock" command that does "chmod g-w $@";
> git-unlock reenables the group-writable bit. Done.

That was what I was thinking of doing (with modestly more cleverness for recursive operation), and maybe some convenience flags for git-commit for automatically unlocking or preserving the lock across a commit.

Cheers, Edward

Previous: Martin LanghoffNext: Avery Pennarun
Message 9 of 11 in “Interest in locking mechanism?”
  1. Edward Z. YangJan 12, 2010
  2. B Smith-MannschottJan 12, 2010
  3. Edward Z. YangJan 12, 2010
  4. Tomas CarneckyJan 12, 2010
  5. Avery PennarunJan 12, 2010
  6. Edward Z. YangJan 12, 2010
  7. Avery PennarunJan 12, 2010
  8. Martin LanghoffJan 12, 2010
  9. Edward Z. YangJan 12, 2010
  10. Avery PennarunJan 12, 2010
  11. Martin LanghoffJan 12, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.