From: Phillip Wood <phillip.wood123@gmail.com>
To: Shubham Kanodia <shubham.kanodia10@gmail.com>,
Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Derrick Stolee <stolee@gmail.com>
Subject: Re: Re*: What's cooking draft as of 2024-09-06 late night
Date: Mon, 9 Sep 2024 10:13:07 +0100 [thread overview]
Message-ID: <125aab1b-d017-45c1-b93c-ee43fef9bd71@gmail.com> (raw)
In-Reply-To: <CAG=Um+0X3Umt-2TQ-BGeefqdGxfVoy2Ug0tGKLycrX=_pj=oJw@mail.gmail.com>
Hi Shubham
On 07/09/2024 20:33, Shubham Kanodia wrote:
>
> I agree — there are rarely reasons to keep a different fetch behavior
> for prefetch vs. fetch all, and `skipFetchAll` should
> do the trick for most use cases. My original goal was to restrict refs
> anyway, I don't work with multiple remotes either.
>
> I'd have perhaps expected these properties to be documented (or at
> least referenced) in the documentation for `git-fetch`.
> The only place `skipFetchAll` is currently documented is in this large
> master list of configs that are easy to miss —
> https://git-scm.com/docs/git-config.
We could perhaps expand the documentation of `git fetch --all` to
mention skipFetchAll
> If there's a consensus, I'll switch to submitting a patch for
> `prefetchref` instead.
I think that would be a useful addition. Given the names of the existing
refspec variables end '.fetch' and '.push' I'd be tempted to call it
'remote.<remote>.prefetch'.
Best Wishes
Phillip
next prev parent reply other threads:[~2024-09-09 9:13 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
2024-09-07 16:42 ` Re*: " Junio C Hamano
2024-09-07 19:33 ` Shubham Kanodia
2024-09-09 9:13 ` Phillip Wood [this message]
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=125aab1b-d017-45c1-b93c-ee43fef9bd71@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).