From: Phillip Wood <phillip.wood123@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org,
Shubham Kanodia <shubham.kanodia10@gmail.com>,
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:14 +0100 [thread overview]
Message-ID: <72635041-576e-42d5-9e12-13e9572b2cf7@gmail.com> (raw)
In-Reply-To: <xmqq8qw3xvob.fsf_-_@gitster.g>
Hi Junio
On 07/09/2024 17:42, Junio C Hamano wrote:
> --- >8 ---
> Subject: doc: remote.*.skip{DefaultUpdate,FetchAll} stops prefetch
>
> Back when 7cc91a2f (Add the configuration option skipFetchAll,
> 2009-11-09) added for the sole purpose of adding skipFetchAll as a
> synonym to skipDefaultUpdate, there was no explanation about the
> reason why it was needed., but these two configuration variables
> mean exactly the same thing.
>
> Also, when we taught the "prefetch" task to "git maintenance" later,
> we did make it pay attention to the setting, but we forgot to
> document it.
>
> Document these variables as synonyms that collectively implements
> the last-one-wins semantics, and also clarify that the prefetch task
> is also controlled by this variable.
>
> Signed-off-by: Junio C Hamano <gitster@pobox.com>
> ---
> * Note that "skipped by default" in the original has been rewritten
> to "skipped" (unconditional), and this is deliberate. When there
> is no conditionality and the behaviour is the only available one,
> it is *not* "by default".
This all sounds sensible, the patch looks good to me
Best Wishes
Phillip
> Documentation/config/remote.txt | 13 +++++++------
> Documentation/git-maintenance.txt | 3 +++
> 2 files changed, 10 insertions(+), 6 deletions(-)
>
> diff --git c/Documentation/config/remote.txt w/Documentation/config/remote.txt
> index 8efc53e836..36e771556c 100644
> --- c/Documentation/config/remote.txt
> +++ w/Documentation/config/remote.txt
> @@ -42,14 +42,15 @@ remote.<name>.mirror::
> as if the `--mirror` option was given on the command line.
>
> remote.<name>.skipDefaultUpdate::
> - If true, this remote will be skipped by default when updating
> - using linkgit:git-fetch[1] or the `update` subcommand of
> - linkgit:git-remote[1].
> + A deprecated synonym to `remote.<name>.skipFetchAll` (if
> + both are set in the configuration files with different
> + values, the value of the last occurrence will be used).
>
> remote.<name>.skipFetchAll::
> - If true, this remote will be skipped by default when updating
> - using linkgit:git-fetch[1] or the `update` subcommand of
> - linkgit:git-remote[1].
> + If true, this remote will be skipped when updating
> + using linkgit:git-fetch[1], the `update` subcommand of
> + linkgit:git-remote[1], and ignored by the prefetch task
> + of `git maitenance`.
>
> remote.<name>.receivepack::
> The default program to execute on the remote side when pushing. See
> diff --git c/Documentation/git-maintenance.txt w/Documentation/git-maintenance.txt
> index 51d0f7e94b..9d96819133 100644
> --- c/Documentation/git-maintenance.txt
> +++ w/Documentation/git-maintenance.txt
> @@ -107,6 +107,9 @@ with the prefetch task, the objects necessary to complete a later real fetch
> would already be obtained, making the real fetch faster. In the ideal case,
> it will just become an update to a bunch of remote-tracking branches without
> any object transfer.
> ++
> +The `remote.<name>.skipFetchAll` configuration can be used to
> +exclude a particular remote from getting prefetched.
>
> gc::
> Clean up unnecessary files and optimize the local repository. "GC"
>
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
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 [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=72635041-576e-42d5-9e12-13e9572b2cf7@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).