* locking (binary) files in git with gitolite
@ 2012-05-27 13:53 Sitaram Chamarty
0 siblings, 0 replies; only message in thread
From: Sitaram Chamarty @ 2012-05-27 13:53 UTC (permalink / raw
To: gitolite, Git Mailing List
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-05-27 13:53 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-05-27 13:53 locking (binary) files in git with gitolite Sitaram Chamarty
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).