Re: [PATCH v2] config: retry acquiring config.lock, configurable via core.configLockTimeout

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 8, 2026, 14:49 UTC
Message-ID: <xmqqa4s1wn7y.fsf@gitster.g>
In-Reply-To: <b5c80d76-5ef4-cf1f-f4e1-78e63cfea81b@gmx.de>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

Show 8 quoted lines

> ... doubt whether the cost of that cache was worth blocking this patch for
> over a month. Lacking such a cozy setting and at this time also lacking
> the leisure to enjoy said beverages, I'd rather go forward with the
> proposed version and move on to more exciting things.
>
> In other words: I consider this patch fine as-is, and in the event that I
> would consider highly unlikely where the cache _really_ bothers anyone, it
> will be an easy patch to remove it.

And until now, we had over a month to see such an add-on patch, or hear argument like the above that such a patch is not needed. That is what I find disturbing the most here.