All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Eric Wong <e@80x24.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] fetch: pass --no-write-fetch-head to subprocesses
Date: Wed, 8 Mar 2023 22:09:59 -0500	[thread overview]
Message-ID: <ZAlOB0XZaGPUJMS7@coredump.intra.peff.net> (raw)
In-Reply-To: <20230308100438.908471-1-e@80x24.org>

On Wed, Mar 08, 2023 at 10:04:38AM +0000, Eric Wong wrote:

> It seems a user would expect this option would work regardless
> of whether it's fetching from a single remote or many.
> 
> Signed-off-by: Eric Wong <e@80x24.org>
> ---
>  I haven't checked if there's other suitable options which could
>  go into add_options_to_argv(); hopefully someone else can check :>

There's at least one that came up before:

  https://lore.kernel.org/git/DM5PR1701MB1724CCBB1AC5CF342BA9ADD5898E9@DM5PR1701MB1724.namprd17.prod.outlook.com/

but it never got turned into a real patch.

This is obviously an error-prone mechanism.  It would be nice if there
was a way to avoid it, but after some discussion in this thread, we
didn't come up with anything clever:

  https://lore.kernel.org/git/20200914121906.GD4705@pflmari/

-Peff

      parent reply	other threads:[~2023-03-09  3:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 10:04 [PATCH] fetch: pass --no-write-fetch-head to subprocesses Eric Wong
2023-03-08 17:41 ` Junio C Hamano
2023-03-08 22:22   ` [PATCH v2] " Eric Wong
2023-03-08 23:13     ` Junio C Hamano
2023-03-08 23:40       ` Junio C Hamano
2023-03-08 23:48         ` Eric Wong
2023-03-09 21:32           ` Junio C Hamano
2023-03-09  3:09 ` Jeff King [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=ZAlOB0XZaGPUJMS7@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=e@80x24.org \
    --cc=git@vger.kernel.org \
    /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.