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

From: Colin Stagner <ask+git@howdoi.land>
Date: Feb 15, 2026, 21:05 UTC
Message-ID: <3e8b0ada-2fd8-497b-afde-5e02fe78a2fa@howdoi.land>
In-Reply-To: <8c588acc-1626-4ebe-824d-319d721537a1@heusel.eu>

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

Show 7 quoted lines

> 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