git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] technical/partial-clone: narrow the one-at-a-time fetch limitation

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 19, 2026, 15:37 UTC
Message-ID
<xmqqcxt566rr.fsf@gitster.g>
In-Reply-To
<20261019023408.13062-1-f@lex.la>
Aleksei Sviridkin <f@lex.la> writes:
> This one got a review in September and no objections, but it is not in
> any branch and not in What's cooking. It still applies to master as is.

I just looked at the patch and shared Elijah's reaction: the wall of text was simply unreadable, and I gave up trying to read it. When there is no active support, "no objections" does not carry much weight and is not very different from "interests nobody".

I do not recall what the situation was back then. But if the reason your messages (not limited to this one) received no reaction was due to especially bad timing (for example, when the mailing list was flooded with AI-generated slop and readers were tired of seeing it), it might make sense to polish the patch to avoid looking like such slop and repost it to get more exposure.

Thanks.
Previous: Aleksei Sviridkin
Message 6 of 6 in “technical/partial-clone: narrow the one-at-a-time fetch limitation”
  1. technical/partial-clone: narrow the one-at-a-time fetch limitationAleksei Sviridkin, Sep 3, 2026
  2. Elijah NewrenSep 3, 2026
  3. Aleksei SviridkinSep 3, 2026
  4. Elijah NewrenSep 3, 2026
  5. Aleksei SviridkinOct 19, 2026
  6. Junio C HamanoOct 19, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.