From: Junio C Hamano <gitster@pobox.com>
To: "Matt Hunter" <m@lfurio.us>
Cc: <git@vger.kernel.org>, "Bence Ferdinandy" <bence@ferdinandy.com>,
"Jeff King" <peff@peff.net>
Subject: Re: [PATCH v2 0/7] Introduce fetch.followRemoteHEAD config variable
Date: Thu, 18 Jun 2026 08:47:01 -0700 [thread overview]
Message-ID: <xmqqmrwrsvey.fsf@gitster.g> (raw)
In-Reply-To: <DJBVYP58YNTU.LQ7VXFIQE84H@lfurio.us> (Matt Hunter's message of "Thu, 18 Jun 2026 00:21:33 -0400")
"Matt Hunter" <m@lfurio.us> writes:
>> Other than that, this looks excellent. Thanks.
>
> Thanks for the great feedback and consideration!
>
> If you like, I can apply the appropriate NEEDSWORK comment, possibly add
> a warning to 'fetch.followRemoteHEAD' parsing (matching the 'remote'
> side), and we can call this good to go for now.
Sounds like a plan. Thanks.
prev parent reply other threads:[~2026-06-18 15:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 16:31 followRemoteHEAD management question Matt Hunter
2026-06-08 23:49 ` Jeff King
2026-06-11 4:12 ` Matt Hunter
2026-06-11 6:01 ` Jeff King
2026-06-11 20:36 ` Bence Ferdinandy
2026-06-12 6:11 ` Matt Hunter
2026-06-12 5:55 ` [PATCH 0/7] Introduce fetch.followRemoteHEAD config option Matt Hunter
2026-06-12 5:55 ` [PATCH 1/7] fetch: fixup set_head advice for warn-if-not-branch Matt Hunter
2026-06-12 5:55 ` [PATCH 2/7] doc: explain fetchRemoteHEADWarn advice Matt Hunter
2026-06-12 5:55 ` [PATCH 3/7] t5510: cleanup remote in followRemoteHEAD dangling ref test Matt Hunter
2026-06-12 5:55 ` [PATCH 4/7] fetch: rename function report_set_head Matt Hunter
2026-06-12 5:55 ` [PATCH 5/7] fetch: refactor do_fetch handling of followRemoteHEAD Matt Hunter
2026-06-12 5:55 ` [PATCH 6/7] fetch: add configuration option fetch.followRemoteHEAD Matt Hunter
2026-06-12 14:00 ` Matt Hunter
2026-06-12 14:17 ` Junio C Hamano
2026-06-13 2:58 ` Matt Hunter
2026-06-12 5:55 ` [PATCH 7/7] fetch: fixup a misaligned comment Matt Hunter
2026-06-16 22:25 ` [PATCH v2 0/7] Introduce fetch.followRemoteHEAD config variable Matt Hunter
2026-06-16 22:25 ` [PATCH v2 1/7] fetch: fixup set_head advice for warn-if-not-branch Matt Hunter
2026-06-16 22:25 ` [PATCH v2 2/7] doc: explain fetchRemoteHEADWarn advice Matt Hunter
2026-06-16 22:25 ` [PATCH v2 3/7] t5510: cleanup remote in followRemoteHEAD dangling ref test Matt Hunter
2026-06-16 22:25 ` [PATCH v2 4/7] fetch: rename function report_set_head Matt Hunter
2026-06-16 22:25 ` [PATCH v2 5/7] fetch: refactor do_fetch handling of followRemoteHEAD Matt Hunter
2026-06-16 22:25 ` [PATCH v2 6/7] fetch: add configuration variable fetch.followRemoteHEAD Matt Hunter
2026-06-16 22:25 ` [PATCH v2 7/7] fetch: fixup a misaligned comment Matt Hunter
2026-06-16 23:18 ` [PATCH v2 0/7] Introduce fetch.followRemoteHEAD config variable Junio C Hamano
2026-06-17 11:51 ` Junio C Hamano
2026-06-18 4:21 ` Matt Hunter
2026-06-18 15:47 ` 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=xmqqmrwrsvey.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=bence@ferdinandy.com \
--cc=git@vger.kernel.org \
--cc=m@lfurio.us \
--cc=peff@peff.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox