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

Re: [regression][bisected] git-subtree remote desynchronization

From
Junio C Hamano <gitster@pobox.com>
Date
Jan 26, 2026, 17:32 UTC
Message-ID
<xmqqy0lki8jb.fsf@gitster.g>
In-Reply-To
<023ae712-8f67-441c-aada-fb5b097ec617@howdoi.land>
Colin Stagner <ask+git@howdoi.land> writes:
Show 8 quoted lines
> On 1/24/26 22:51, Junio C Hamano wrote:
>
>> Unless a fix materializes and gets verified before -rc2 (scheduled for
>> coming Tuesday), we should revert the merge of the problematic
>> topic.
> Understood and no worries. This is a surprisingly complicated issue, and 
> while I've made progress I don't think I'll have a fix that is mergeable 
> by Tuesday. Feel free to revert as needed.
Done.  Thanks.
Previous: Colin Stagner
Message 7 of 7 in “[regression][bisected] git-subtree remote desynchronization”
  1. Christian HeuselJan 24, 2026
  2. Junio C HamanoJan 25, 2026
  3. Junio C HamanoJan 25, 2026
  4. Colin StagnerJan 26, 2026
  5. Christian HeuselJan 26, 2026
  6. Colin StagnerFeb 15, 2026
  7. Junio C HamanoJan 26, 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.