From: george@mail.dietrich.pub
To: ask+git@howdoi.land
Cc: george@mail.dietrich.pub, git@vger.kernel.org
Subject: Re: [Bug] Git subtree regression
Date: Tue, 17 Feb 2026 23:29:18 -0500 [thread overview]
Message-ID: <20260218042918.330374-1-george@mail.dietrich.pub> (raw)
In-Reply-To: <8d5212b5-3088-4b73-a849-f1c297e06157@howdoi.land>
Ahh bummer, thanks for the follow up. I'm on arch and don't seem to suffer from the same recursion limitation as debian/ubuntu do. Because of that I'll defer checking out that set of patches to someone else.
I did however checkout the other and can confirm it looks good! I went thru each of the components and asserted the split hash matches the latest commit on each of the related repos. Also asserted `subtree push` results in an `Everything up to date` message. Thanks again for all your work on this.
prev parent reply other threads:[~2026-02-18 4:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-26 19:58 [Bug] Git subtree regression dev
2025-12-30 17:07 ` george
2026-01-04 4:52 ` Colin Stagner
2026-01-04 14:27 ` george
2026-01-05 3:36 ` Colin Stagner
2026-01-06 4:55 ` george
2026-01-10 1:25 ` Colin Stagner
2026-01-10 17:22 ` george
2026-02-15 20:36 ` Colin Stagner
2026-02-16 21:25 ` D. Ben Knoble
2026-02-18 4:29 ` george [this message]
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=20260218042918.330374-1-george@mail.dietrich.pub \
--to=george@mail.dietrich.pub \
--cc=ask+git@howdoi.land \
--cc=git@vger.kernel.org \
/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