public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Colin Stagner <ask+git@howdoi•land>
To: Christian Heusel <christian@heusel•eu>
Cc: Junio C Hamano <gitster@pobox•com>,
	git@vger•kernel.org, Christian Hesse <list@eworm•de>
Subject: Re: [regression][bisected] git-subtree remote desynchronization
Date: Sun, 15 Feb 2026 15:05:52 -0600	[thread overview]
Message-ID: <3e8b0ada-2fd8-497b-afde-5e02fe78a2fa@howdoi.land> (raw)
In-Reply-To: <8c588acc-1626-4ebe-824d-319d721537a1@heusel.eu>

On 1/26/26 08:12, Christian Heusel wrote:

> On 26/01/25 11:14PM, Colin Stagner wrote:
>> I have made some progress on a fix, but I have not yet achieved 100% hash
>> equivalence across the board. The bisected patch will likely be reverted
>> while I work on a more permanent solution.
> 
> I guess that is for you and Junio to judge, but rushing a fix sounds
> like unneccesary risk for an optimization.

Chris,

I've CC'd you on some proposed changes to remove the git-subtree 
"should_ignore_subtree_split_commit" logic.

I have tested both of my patch series [1], [2] against every 
subdirectory of your aur.git repo [3]. I checked the split of every 
top-level directory as follows:

     for d in *
     do
       test -d "$d" || continue;
       echo >>split-results "$d  $(git subtree split -P "$d")"
     done

I compared the results to git 2.43.7 and found no changes. I would 
appreciate some more eyeballs and testing on this series to make sure it 
doesn't introduce any breakage.

Thanks,

Colin

[1]: 20260215201748.889866-1-ask+git@howdoi•land

[2]: 20260215201906.889951-1-ask+git@howdoi•land

[3]: https://github.com/christian-heusel/aur.git

next prev parent reply	other threads:[~2026-02-15 21:06 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
2026-01-26  5:14     ` Colin Stagner
2026-01-26 14:12       ` Christian Heusel
2026-02-15 21:05         ` Colin Stagner [this message]
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=3e8b0ada-2fd8-497b-afde-5e02fe78a2fa@howdoi.land \
    --to=ask+git@howdoi$(echo .)land \
    --cc=christian@heusel$(echo .)eu \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitster@pobox$(echo .)com \
    --cc=list@eworm$(echo .)de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox