From: Patrick Steinhardt <ps@pks.im>
To: Justin Tobler <jltobler@gmail.com>
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
Wolfgang Kritzinger <wkritzinger@atlassian.com>,
git@vger.kernel.org
Subject: Re: Performance regression in connectivity check during receive-pack (git 2.54)
Date: Tue, 4 Aug 2026 08:19:45 +0200 [thread overview]
Message-ID: <anGEgUrzzQYzEK_K@pks.im> (raw)
In-Reply-To: <amd4yR3EEn_fVZcm@denethor>
On Mon, Jul 27, 2026 at 10:45:46AM -0500, Justin Tobler wrote:
> On 26/07/24 05:46AM, Patrick Steinhardt wrote:
[snip]
> > I think overall this could simplify some of the design, and it makes a
> > bunch of issues that I have been struggling with go away. The devil may
> > be in the details of course, but I think transitioning towards this
> > should be doable.
>
> I am certainly a fan of this direction. We do lose some flexibility in
> terms of supporting alternates more generically, but I'm not sure
> supporting alternates of different source types in the same repo would
> be something we want anyways in practice due to the additional
> complexity.
True. But if we ever find that we actually want that flexibility we
don't paint ourselves into a corner, either, as it is rather trivial to
introduce another source type that allows us to mix and match different
sources.
Patrick
next prev parent reply other threads:[~2026-08-04 6:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 3:17 Performance regression in connectivity check during receive-pack (git 2.54) Wolfgang Kritzinger
2026-07-21 3:57 ` Jeff King
2026-07-21 5:05 ` Taylor Blau
2026-07-21 14:40 ` Junio C Hamano
2026-07-22 11:49 ` Patrick Steinhardt
2026-07-22 15:49 ` Junio C Hamano
2026-07-23 10:49 ` Jeff King
2026-07-24 3:46 ` Patrick Steinhardt
2026-07-26 8:51 ` Jeff King
2026-07-27 15:45 ` Justin Tobler
2026-08-04 6:19 ` Patrick Steinhardt [this message]
2026-07-23 10:46 ` Jeff King
2026-07-23 10:39 ` Jeff King
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=anGEgUrzzQYzEK_K@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jltobler@gmail.com \
--cc=peff@peff.net \
--cc=wkritzinger@atlassian.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.