From: Junio C Hamano <gitster@pobox.com>
To: Christian Heusel <christian@heusel.eu>
Cc: Colin Stagner <ask+git@howdoi.land>,
git@vger.kernel.org, Christian Hesse <list@eworm.de>
Subject: Re: [regression][bisected] git-subtree remote desynchronization
Date: Sat, 24 Jan 2026 20:51:51 -0800 [thread overview]
Message-ID: <xmqqecnel2fs.fsf@gitster.g> (raw)
In-Reply-To: <xmqqikcql8cq.fsf@gitster.g> (Junio C. Hamano's message of "Sat, 24 Jan 2026 18:44:05 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Thanks for noticing and reporting a regression before the change got
> released in an official release.
>
> If a fix materializes and gets verified before -rc2 (scheduled for
> coming Tuesday), we should revert the merge of the problematic
> topic.
Oops, sorry for an obvious typo. "If" -> "Unless", of course.
next prev parent reply other threads:[~2026-01-25 4:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-24 11:43 [regression][bisected] git-subtree remote desynchronization Christian Heusel
2026-01-25 2:44 ` Junio C Hamano
2026-01-25 4:51 ` Junio C Hamano [this message]
2026-01-26 5:14 ` Colin Stagner
2026-01-26 14:12 ` Christian Heusel
2026-02-15 21:05 ` Colin Stagner
2026-01-26 17:32 ` 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=xmqqecnel2fs.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ask+git@howdoi.land \
--cc=christian@heusel.eu \
--cc=git@vger.kernel.org \
--cc=list@eworm.de \
/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