public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Pegorari <lorenzo.pegorari2002@gmail.com>
To: git@vger.kernel.org
Cc: Christian Couder <christian.couder@gmail.com>,
	Karthik Nayak <karthik.188@gmail.com>,
	Justin Tobler <jltobler@gmail.com>,
	Siddharth Asthana <siddharthasthana31@gmail.com>,
	Ayush Chandekar <ayu.chandekar@gmail.com>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [GSoC] extensions.partialClone and promisor remote fetch order
Date: Sat, 7 Mar 2026 15:58:05 +0100	[thread overview]
Message-ID: <aaw8_U0hOEag4WDO@lorenzo-VM> (raw)
In-Reply-To: <aavvwfZllMWUwIl3@lorenzo-VM>

On Sat, Mar 07, 2026 at 10:28:33AM +0100, Lorenzo Pegorari wrote:
> Hi everyone. In the past weeks I deeply studied the documentation
> regarding the GSoC'26 idea "Implement promisor remote fetch ordering". I
> am preparing a proposal that is as detailed as possible, and that tries
> to answer to as many questions as possible. I am also experimenting a
> lot with multiple promisor remotes configurations, and creating some
> examples that I will showcase in my proposal.
> 
> 
> I have a question regarding the interaction between the config
> "extensions.partialClone" and a possible fetch ordering mechanism:
>  * from my understanding, and from my personal tests, it looks like
>    "extensions.partialClone" is not essential when working with multiple
>    promisor remotes. Having these promisor remotes setted up with
>    "remote.<name>.promisor" and "remote.<name>.partialCloneFilter" seems
>    sufficient. In this case, the promisor remotes will be tried one
>    after the other, in the order in which they appear in the config.
>  * if "extensions.partialClone" is present, then the promisor remote
>    configured using the "extensions.partialClone" config var will be the
>    last one tried when fetching an object.
> 
> 1. is what I explained correct?
> 2. when the fetch ordering mechanism will be added, this config var will
>    not be useful anymore. How should it be handled? It probably can't
>    just be removed, so the fetch ordering mechanism should be flexible
>    enough to handle a situation where "extensions.partialClone" is
>    present, correct?
> 
> 
> Thanks,
> Lorenzo

Also, I see that "extensions.partialClone" is already necessary "to
prevent older versions of git from failing mid-operation because of
missing objects that they cannot handle".

This is one of the last issues that I still have to iron out before I
can send a satisfactory proposal draft.

[1]: https://git-scm.com/docs/git-config#Documentation/git-config.txt-partialClone
[2]: https://git-scm.com/docs/git-config#Documentation/git-config.txt-partialClone

  reply	other threads:[~2026-03-07 14:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07  9:28 [GSoC] extensions.partialClone and promisor remote fetch order Lorenzo Pegorari
2026-03-07 14:58 ` Lorenzo Pegorari [this message]
2026-03-09 13:40 ` Christian Couder
2026-03-10 18:32   ` Lorenzo Pegorari

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=aaw8_U0hOEag4WDO@lorenzo-VM \
    --to=lorenzo.pegorari2002@gmail.com \
    --cc=ayu.chandekar@gmail.com \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jltobler@gmail.com \
    --cc=karthik.188@gmail.com \
    --cc=siddharthasthana31@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