git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: "D. Ben Knoble" <ben.knoble@gmail.com>,
	 Ran Ari-Gur <ran.arigur+git@samsara.com>,
	 git@vger.kernel.org,  "raa.lkml@gmail.com" <raa.lkml@gmail.com>
Subject: Re: [BUG] `git clone '-c KEY=VALUE'` no longer works
Date: Sun, 30 Nov 2025 10:11:06 -0800	[thread overview]
Message-ID: <xmqqzf83bdc5.fsf@gitster.g> (raw)
In-Reply-To: <20251130134930.GB199421@coredump.intra.peff.net> (Jeff King's message of "Sun, 30 Nov 2025 08:49:30 -0500")

Jeff King <peff@peff.net> writes:

> That's about where I'm at, though I'm a little worried by Dscho's
> mention that apparently git-lfs has the same problem. So maybe it's more
> widespread than I am giving it credit for?

Reading <https://github.com/git-for-windows/git/issues/5972>, I
think the mention of LFS in Dscho's message on this list was a
red-herring, as corrected by Dscho himself at

  https://github.com/git-for-windows/git/issues/5972#issuecomment-3577520017

I do not know if buggily constructed command line by Atlassian
Bamboo is something we want to bend over backwards to help papering
over, but probably not.

> I dunno. I certainly do not want to get into a deprecation period and
> all of that mess. Maybe the breakage in v2.52.0 would be enough for
> callers to notice and fix their invocations, and we could just quietly
> remove the hack later? But then, I am not sure what makes "later" any
> better than "now".

Yes.  Let's write it off as an inadvertent bugfix ;-)

Thanks.

  reply	other threads:[~2025-11-30 18:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24  5:23 [BUG] `git clone '-c KEY=VALUE'` no longer works Ran Ari-Gur
2025-11-24 16:20 ` D. Ben Knoble
2025-11-24 21:19   ` Junio C Hamano
2025-11-24 23:55     ` Jeff King
2025-11-25  1:27       ` Junio C Hamano
2025-11-25 22:03         ` Junio C Hamano
2025-11-26 15:02           ` Jeff King
2025-11-26 17:06             ` Junio C Hamano
2025-11-30 13:49               ` Jeff King
2025-11-30 18:11                 ` Junio C Hamano [this message]
2025-11-26 14:53         ` Jeff King
2025-11-26 17:08           ` Junio C Hamano
2025-11-24 22:57   ` Jeff King
2025-11-25 20:16   ` Johannes Schindelin

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=xmqqzf83bdc5.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=ben.knoble@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=raa.lkml@gmail.com \
    --cc=ran.arigur+git@samsara.com \
    /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;
as well as URLs for NNTP newsgroup(s).