All of lore.kernel.org
 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: Wed, 26 Nov 2025 09:08:32 -0800	[thread overview]
Message-ID: <xmqqpl94oh67.fsf@gitster.g> (raw)
In-Reply-To: <20251126145320.GA4143292@coredump.intra.peff.net> (Jeff King's message of "Wed, 26 Nov 2025 09:53:20 -0500")

Jeff King <peff@peff.net> writes:

> I would be more sympathetic if the original report was "it is useful for
> so-and-so reason to do this whitespace stripping". But it really sounds
> like the problem was some caller doing something like (in perl
> pseudo-code):
>
>   system("git", "clone", "-c $key", $repo);
>
> instead of:
>
>   system("git", "clone", "-c", $key, $repo);
>
> which is just a bug that happened to work in this limited instance.
>
> So my inclination would be to leave it be, because I do not think it
> merits the time. But if somebody else wants to go for it, I will not
> stop them. ;)

;-)  I might, as it would consume my time as well as theirs.

  reply	other threads:[~2025-11-26 17:08 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
2025-11-26 14:53         ` Jeff King
2025-11-26 17:08           ` Junio C Hamano [this message]
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=xmqqpl94oh67.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 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.