All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bence Ferdinandy" <bence@ferdinandy.com>
To: "Jeff King" <peff@peff.net>,
	"brian m. carlson" <sandals@crustytoothpaste.net>
Cc: <git@vger.kernel.org>, <felipe.contreras@gmail.com>
Subject: Re: feature request: set remote/HEAD with fetch
Date: Sat, 17 Aug 2024 21:00:10 +0200	[thread overview]
Message-ID: <D3IF2EVJPNMX.CFNKJQDPHZQ0@ferdinandy.com> (raw)
In-Reply-To: <20240817050240.GA29822@coredump.intra.peff.net>


> There was discussion a while ago that proposed a tri-state config
> option: never update the remote head on fetch, always do so, or add it
> only when missing:
>
>   https://lore.kernel.org/git/20201118091219.3341585-1-felipe.contreras@gmail.com/

Thanks for linking that, I didn't think about searching for old discussion
before writing ...

>
> I think that is a good first step, as we could stop there and leave the
> default at "never" without any compatibility issues (and/or contemplate
> a change in the default as a separate step).
>
> I don't think the patch in that thread is likely to go anywhere at this
> point, but if somebody wanted to pick it up, I think everybody was
> positive on the general direction.

My C skills aren't great (probably an overstatement), but if Felipe or somebody
else more qualified than me doesn't want to pick this up, I'm willing to give
it a shot based on the Felipe's patch. It will take some time though :)

Thanks,
Bence

  reply	other threads:[~2024-08-17 19:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-16 11:53 feature request: set remote/HEAD with fetch Bence Ferdinandy
2024-08-16 21:55 ` brian m. carlson
2024-08-16 22:10   ` Junio C Hamano
2024-08-17  5:02   ` Jeff King
2024-08-17 19:00     ` Bence Ferdinandy [this message]
2024-08-19 16:40       ` Johannes Schindelin
2024-08-20 21:38         ` Bence Ferdinandy

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=D3IF2EVJPNMX.CFNKJQDPHZQ0@ferdinandy.com \
    --to=bence@ferdinandy.com \
    --cc=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=sandals@crustytoothpaste.net \
    /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.