Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Joerg Thalheim <joerg@thalheim.io>,
	 git@vger.kernel.org,  Patrick Steinhardt <ps@pks.im>
Subject: Re: [PATCH v2] config: retry acquiring config.lock, configurable via core.configLockTimeout
Date: Thu, 28 May 2026 21:23:14 +0900	[thread overview]
Message-ID: <875x47u3il.fsf@gitster.g> (raw)
In-Reply-To: <f449d0db-0434-f870-c69f-793f2b096816@gmx.de> (Johannes Schindelin's message of "Thu, 28 May 2026 13:51:42 +0200 (CEST)")

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

> Footnote *1*: In general, I am quite wary of unit-less numbers in
> configurations.

Hear, hear.

I do not like unit-less names for variables that store numbers, not
just configuration but in-code variables.  In the longer run we want
to clean these up.  In-code variables are much easier to clean-up
than end-user facing configuration variable names, of course.


      reply	other threads:[~2026-05-28 12:23 UTC|newest]

Thread overview: 13+ 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-05-28 11:51             ` Johannes Schindelin
2026-05-28 12:23               ` Junio C Hamano [this message]

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=875x47u3il.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox