From: Phillip Wood <phillip.wood123@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Shubham Kanodia <shubham.kanodia10@gmail.com>,
Derrick Stolee <stolee@gmail.com>
Subject: Re: What's cooking draft as of 2024-09-06 late night
Date: Sat, 7 Sep 2024 10:17:32 +0100 [thread overview]
Message-ID: <899eb2c2-bb18-4666-98d8-9255dedfac53@gmail.com> (raw)
In-Reply-To: <xmqq7cboyq9s.fsf@gitster.g>
Hi Junio and Shubham
On 07/09/2024 06:41, Junio C Hamano wrote:
> Will merge to 'next'?
> - sk/enable-prefetch-per-remote 09-05 #1
> <pull.1779.v4.git.1725565398681.gitgitgadget@gmail.com>
I've just taken a look at this and I'm left wondering why one would want
to skip prefetching from a remote but still fetch from it with "git
fetch --all". I set remote.<remote>.skipFetchAll for the remotes I don't
want to prefetch. We also have remote.<remote>.skipDefaultUpdate I don't
know offhand if that prevents a remote from being prefetched as well.
I think being able to specify which refs are prefectched would be
useful. Overloading remote.<remote>.prefetch to be a boolean or a
refspec would complicate the implementation so maybe we'd be better just
supporting refspecs and update the maintenance documentation to point
users to the existing config for skipping prefetches.
Best Wishes
Phillip
next prev parent reply other threads:[~2024-09-07 9:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-07 5:41 What's cooking draft as of 2024-09-06 late night Junio C Hamano
2024-09-07 9:17 ` Phillip Wood [this message]
2024-09-07 16:42 ` Re*: " Junio C Hamano
2024-09-07 19:33 ` Shubham Kanodia
2024-09-09 9:13 ` Phillip Wood
2024-09-09 15:53 ` Junio C Hamano
2024-09-10 8:42 ` Phillip Wood
2024-09-10 14:41 ` Junio C Hamano
2024-09-09 9:13 ` Phillip Wood
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=899eb2c2-bb18-4666-98d8-9255dedfac53@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=phillip.wood@dunelm.org.uk \
--cc=shubham.kanodia10@gmail.com \
--cc=stolee@gmail.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).