From: Kaartic Sivaraam <kaartic.sivaraam@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
Christian Couder <christian.couder@gmail.com>
Cc: git@vger.kernel.org, Hussain Sitamouwala <husainsitamuwala21@gmail.com>
Subject: Re: [PATCH] partial-clone: document promisor remote fetch ordering
Date: Fri, 13 Nov 2026 19:23:21 +0530 [thread overview]
Message-ID: <1c124d5d-790b-4d22-af22-c53573e6d2ec@gmail.com> (raw)
In-Reply-To: <xmqq5wy89rq6.fsf@gitster.g>
On 11/8/26 04:25, Junio C Hamano wrote:
> Hussain Sitamouwala <husainsitamuwala21@gmail.com> writes:
>
> It seems there are multiple people sending messages with words like
> "promisor", "fetch", "order", and "Outreachy" on their "Subject:"
> fairly recently, but are you in charge of herding these folks, or is
> somebody else helping them? Without knowing if there is somebody
> central coordinating these that I can ask about, it is hard to tell
> if these people are making coherent effort to achieve something
> worthwhile, or if they are just randomly banging the door.
>
The patches surrounding promisor-remote are coming through because we
had proposed the following project for this year's Outreachy round.
Implement promisor remote fetch ordering
When a Git repository is configured with multiple promisor remotes,
there’s currently no mechanism to specify or optimize the order in
which these remotes should be queried when fetching missing objects.
Different remotes may have different performance characteristics,
costs, or reliability, making fetch order an important consideration.
This project aims to implement a fetch ordering mechanism for multiple
promisor remotes. The order could be:
- Configured locally by the client
- Advertised by servers through the promisor-remote protocol
The key challenge is designing a flexible system that allows servers
to communicate their preferred fetch order to clients (to ensure
optimal performance and cost management).
See also:
https://lore.kernel.org/git/CAP8UFD3kd=6QHp2oB+t+g-2D8bY-Oe5+_Vk+RJeaCa_xhxGrsA@mail.gmail.com/
I have volunteered to mentor the same and Chrisitian has mentioned that
he'll help with the project. Feel free to ping me too in case you see
anything around this you need some help with.
Sorry for the late response. I just thought I'll fill in with the
context in case it helps.
--
Sivaraam
next prev parent reply other threads:[~2026-11-13 13:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 15:04 [PATCH] partial-clone: document promisor remote fetch ordering Hussain Sitamouwala
2026-11-07 22:55 ` Junio C Hamano
2026-11-13 13:53 ` Kaartic Sivaraam [this message]
2026-11-13 14:23 ` Hussain Sitamouwala
2026-11-13 14:37 ` Hussain Sitamouwala
2026-11-14 15:35 ` Kaartic Sivaraam
2026-11-14 15:32 ` Kaartic Sivaraam
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=1c124d5d-790b-4d22-af22-c53573e6d2ec@gmail.com \
--to=kaartic.sivaraam@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=husainsitamuwala21@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