Re: [PATCH] git: add --no-optional-locks option

From: Jeff Hostetler <git@jeffhostetler.com>
Date: Sep 26, 2017, 14:44 UTC
Message-ID: <2646e18b-473e-17bc-fa92-1d7ef5f46055@jeffhostetler.com>
In-Reply-To: <alpine.DEB.2.21.1.1709251816120.40514@virtualbox>

On 9/25/2017 12:17 PM, Johannes Schindelin wrote:

Show 15 quoted lines

> Hi Kaartic,
> 
> On Sun, 24 Sep 2017, Kaartic Sivaraam wrote:
> 
>> On Thursday 21 September 2017 10:02 AM, Jeff King wrote:
>>> Some tools like IDEs or fancy editors may periodically run commands
>>> like "git status" in the background to keep track of the state of the
>>> repository.
>>
>> I might be missing something, shouldn't the IDEs be encouraged to use
>> libgit2 instead? I thought it was meant for these use cases.
> 
> There are pros and cons. Visual Studio moved away from libgit2 e.g. to
> support SSH (back then, libgit2 did not support spawning processes, I have
> no idea whether that changed in the meantime).

There were other issues besides feature parity. The big one for VS was that it moved the git computations into a separate process and address space. You can't easily read/modify/write a 500MB .git/index file into memory (with however many copies of the data that that creates) in a 32-bit process.