From: Junio C Hamano <gitster@pobox.com>
To: Aleksei Sviridkin <f@lex.la>
Cc: git@vger.kernel.org, Elijah Newren <newren@gmail.com>
Subject: Re: [PATCH] technical/partial-clone: narrow the one-at-a-time fetch limitation
Date: Mon, 19 Oct 2026 08:37:28 -0700 [thread overview]
Message-ID: <xmqqcxt566rr.fsf@gitster.g> (raw)
In-Reply-To: <20261019023408.13062-1-f@lex.la> (Aleksei Sviridkin's message of "Mon, 19 Oct 2026 05:34:08 +0300")
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.
next prev parent reply other threads:[~2026-10-19 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 12:55 [PATCH] technical/partial-clone: narrow the one-at-a-time fetch limitation Aleksei Sviridkin
2026-09-03 16:12 ` Elijah Newren
2026-09-03 20:00 ` Aleksei Sviridkin
2026-09-03 23:03 ` Elijah Newren
2026-10-19 2:34 ` Aleksei Sviridkin
2026-10-19 15:37 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-10-19 16:03 Aleksei Sviridkin
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=xmqqcxt566rr.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=f@lex.la \
--cc=git@vger.kernel.org \
--cc=newren@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.