{"thread":{"id":"30636","subject":"locking (binary) files in git with gitolite","startedAt":"2012-05-27T13:53:19Z","lastAt":"2012-05-27T13:53:19Z","messageCount":1,"participants":["Sitaram Chamarty"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"192281","messageId":"CAMK1S_jM=QTMjp7pJLCMxZ12F8q4-WmdPDEEpPT-+8ouYXAO2g@mail.gmail.com","threadId":"30636","inReplyTo":null,"subject":"locking (binary) files in git with gitolite","fromName":"Sitaram Chamarty","fromEmail":"sitaramc@gmail.com","sentAt":"2012-05-27T13:53:19Z","receivedAt":"2012-05-27T13:53:19Z","isPatch":false,"sender":{"key":"sitaramc@gmail.com","avatar":"https://avatars.githubusercontent.com/u/43316?v=4"},"body":"One of the groups at $DAYJOB indicated that lack of file locking was a\nshow stopper for using git itself, due to the number of binary\nartefacts (images, ODTs etc) they have and the fact that prevention is\nfar, *far* better than cure when it comes to merging those animals :-)\n\nThinking about it, it struck me that most corporate setups have\nexactly one canonical repo/source of truth and all devs clone\nfrom/push to it, and so it ought to be possible to do something about\nlocking in this limited case.\n\nAnyway, the end result of all this is here:\nhttp://sitaramc.github.com/gitolite/locking.html.  You'll need the\nlatest tip from \"master\" on gitolite if you want to use it.\n\nHope this helps someone.  Especially if you're already using gitolite\n(v3.x) it ought to be relatively painless to try out.\n\n-- \nSitaram\n"}]}