From: Igor Wiedler <iwiedler@gitlab.com>
To: gitster@pobox.com
Cc: git@vger.kernel.org, ps@pks.im
Subject: Re: What's cooking in git.git (Oct 2026, #09)
Date: Thu, 29 Oct 2026 11:27:55 +0100 [thread overview]
Message-ID: <20261029102756.35612-1-iwiedler@gitlab.com> (raw)
In-Reply-To: <xmqqy0blwbyt.fsf@gitster.g>
On Sun, Oct 25, 2026 at 05:18:50PM -0700, Junio C Hamano wrote:
> * iw/connected-deepen-fetch-no-alternate-refs (2026-10-19) 2 commits
> - odb: ignore refs of shallow and grafted alternates
> - connected: negate alternate refs in deepening fetches too
>
> The post-fetch connectivity check in 'git fetch' has been corrected
> to avoid passing alternate refs as positive revisions during a
> deepening fetch, plugging a severe performance bug.
>
> Expecting a reroll.
> cf. <20261020075536.49286-1-iwiedler@gitlab.com>
> cf. <ats6VLXUqKwKZzIY@pks.im>
There have been no code changes since v3 was reviewed. Do you want a
reroll to fix the threading of the patches under the cover letter, or
is there something else I missed?
next prev parent reply other threads:[~2026-10-29 10:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 0:18 What's cooking in git.git (Oct 2026, #09) Junio C Hamano
2026-10-29 10:27 ` Igor Wiedler [this message]
2026-10-29 14:35 ` Junio C Hamano
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=20261029102756.35612-1-iwiedler@gitlab.com \
--to=iwiedler@gitlab.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ps@pks.im \
/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