Re: [PATCH 0/1] Fix UX issue with commit-graph.lock

Derrick Stolee writes: >> Also, can't we tell why we failed to acquire the lock at step #1? >> Do we only get a NULL that says "I am not telling you why, but we >> failed to lock"? > > To tell why we failed to acquire the lock, we could inspect > "errno". However, this requires

Re: [PATCH 0/1] Fix UX issue with commit-graph.lock

On 5/10/2018 3:00 AM, Junio C Hamano wrote: Derrick Stolee writes: We use the lockfile API to avoid multiple Git processes from writing to the commit-graph file in the .git/objects/info directory. In some cases, this directory may not exist, so we check for its

Re: [PATCH 0/1] Fix UX issue with commit-graph.lock

Derrick Stolee writes: > We use the lockfile API to avoid multiple Git processes from writing to > the commit-graph file in the .git/objects/info directory. In some cases, > this directory may not exist, so we check for its existence. > > The existing code does the

Re: [PATCH 0/1] Fix UX issue with commit-graph.lock

On Wed, May 9, 2018 at 4:15 PM, Derrick Stolee wrote: > We use the lockfile API to avoid multiple Git processes from writing to > the commit-graph file in the .git/objects/info directory. In some cases, > this directory may not exist, so we check for its existence. > > The

[PATCH 0/1] Fix UX issue with commit-graph.lock

We use the lockfile API to avoid multiple Git processes from writing to the commit-graph file in the .git/objects/info directory. In some cases, this directory may not exist, so we check for its existence. The existing code does the following when acquiring the lock: 1. Try to acquire the lock.