Re: Re*: What's cooking draft as of 2024-09-06 late night

From: Phillip Wood <phillip.wood123@gmail.com>
Date: Sep 9, 2024, 09:13 UTC
Message-ID: <125aab1b-d017-45c1-b93c-ee43fef9bd71@gmail.com>
In-Reply-To: <CAG=Um+0X3Umt-2TQ-BGeefqdGxfVoy2Ug0tGKLycrX=_pj=oJw@mail.gmail.com>

Hi Shubham

On 07/09/2024 20:33, Shubham Kanodia wrote:

Show 11 quoted lines

> 
> 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