From: Stefan Beller <sbeller@google.com>
Date: Wed, 10 Jun 2015 15:22:14 GMT
Subject: Re: git lock files (Was: GIT for Microsoft Access projects)
Message-ID: <CAGZ79kYhgBaY5UpmfK=amfM56c61vcUu8=ofagG=nPwqkPt2rg@mail.gmail.com>
In-Reply-To: <20150610074733.GM30511@paksenarrion.iveqy.com>

On Wed, Jun 10, 2015 at 12:47 AM, Fredrik Gustafsson <iveqy@iveqy.com> wrote:
> On Tue, Jun 09, 2015 at 10:19:43AM -0700, Stefan Beller wrote:
>> Just because Git allows distributed workflows, doesn't mean we
>> should only focus on being distributed IMHO.
>>
>> The question for content not being mergable easily pops up all
>> the time. (Game/Graphics designers, documents, all this binary
>> stuff, where there is no good merge driver).
>>
>> I could imagine a "git lock" command which looks like this:
>
> You do know that gitolite has locking functionality?
>

Yes, and it's cooking its own thing, it's not upstream (in git core I mean)

Locking is useful not just when using gitolite, but any hosting
solution I believe.