From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Patrick Steinhardt <ps@pks.im>,
Joerg Thalheim <joerg@thalheim.io>,
git@vger.kernel.org
Subject: Re: [PATCH v2] config: retry acquiring config.lock, configurable via core.configLockTimeout
Date: Wed, 08 Jul 2026 07:49:21 -0700 [thread overview]
Message-ID: <xmqqa4s1wn7y.fsf@gitster.g> (raw)
In-Reply-To: <b5c80d76-5ef4-cf1f-f4e1-78e63cfea81b@gmx.de> (Johannes Schindelin's message of "Wed, 8 Jul 2026 09:32:41 +0200 (CEST)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> ... 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.
next prev parent reply other threads:[~2026-07-08 14:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 10:01 [PATCH] config: retry acquiring config.lock for 100ms Joerg Thalheim
2026-04-03 17:53 ` Junio C Hamano
2026-04-08 10:34 ` Patrick Steinhardt
2026-05-11 2:32 ` Junio C Hamano
2026-05-11 7:33 ` Patrick Steinhardt
2026-05-11 9:06 ` Jörg Thalheim
2026-05-11 10:01 ` Patrick Steinhardt
2026-05-17 11:27 ` Johannes Schindelin
2026-05-17 13:21 ` [PATCH v2] config: retry acquiring config.lock, configurable via core.configLockTimeout Joerg Thalheim
2026-05-18 0:46 ` Junio C Hamano
2026-05-18 8:07 ` Patrick Steinhardt
2026-07-08 7:32 ` Johannes Schindelin
2026-07-08 14:49 ` Junio C Hamano [this message]
2026-05-28 11:51 ` Johannes Schindelin
2026-05-28 12:23 ` Junio C Hamano
2026-07-07 11:39 ` Johannes Schindelin
2026-07-07 18:16 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqa4s1wn7y.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=joerg@thalheim.io \
--cc=ps@pks.im \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.