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

locking (binary) files in git with gitolite

From
Sitaram Chamarty <sitaramc@gmail.com>
Date
May 27, 2012, 13:53 UTC
Message-ID
<CAMK1S_jM=QTMjp7pJLCMxZ12F8q4-WmdPDEEpPT-+8ouYXAO2g@mail.gmail.com>

One of the groups at $DAYJOB indicated that lack of file locking was a show stopper for using git itself, due to the number of binary artefacts (images, ODTs etc) they have and the fact that prevention is far, *far* better than cure when it comes to merging those animals :-)

Thinking about it, it struck me that most corporate setups have exactly one canonical repo/source of truth and all devs clone from/push to it, and so it ought to be possible to do something about locking in this limited case.

Anyway, the end result of all this is here: http://sitaramc.github.com/gitolite/locking.html. You'll need the latest tip from "master" on gitolite if you want to use it.

Hope this helps someone. Especially if you're already using gitolite (v3.x) it ought to be relatively painless to try out.

-- 
Sitaram
Message 1 of 1 in “locking (binary) files in git with gitolite”
  1. Sitaram ChamartyMay 27, 2012

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.