{"thread":{"id":"63937","subject":"Fatal error in git subtree split","startedAt":"2025-08-09T22:24:12Z","lastAt":"2025-08-09T22:24:12Z","messageCount":1,"participants":["Sergey Poznyak"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"523874","messageId":"filx6Yt3bQSp1GJwOQKS6cZwaPFfFn5TgcuH0fv1kS3Wgo0xSKxhXDYs6zUm8f_9tZCtF-scyAhFi7dTl3q44w5RkM99QH8gR8RJB5UA7m4=@protonmail.com","threadId":"63937","inReplyTo":null,"subject":"Fatal error in git subtree split","fromName":"Sergey Poznyak","fromEmail":"sergeypoznyak@protonmail.com","sentAt":"2025-08-09T22:24:06Z","receivedAt":"2025-08-09T22:24:12Z","isPatch":false,"sender":{"key":"sergeypoznyak@protonmail.com","avatar":null},"body":"Hello,\n\nI'm trying to split a part of my repo into a separate tree using this command:\n\n=====\n$ git subtree split --debug --prefix=common/container/xarr -b xarr\n---\ntruncated output\n---\nprogress: 16/161 (15) [0]\nProcessing commit: e618ad95203d72380cd38124b446dfd71a663e86\n  parents: e22e667e27a77d22f9b2091df7e7f16e47808a9a \n  newparents: \n  tree is: \nfatal: no new revisions were found\n=====\n\n\n\nIt always stops at this commit. I think the problem is in the next commit though, which is a merge created by git subtree add (without squash) a long time ago that I did vendor in an external library.\nThe merge commit looks like this:\n\n=====\n$ git show 32d21757c1e4446cc87ddb2e93c4d49c0d205eb3\n\ncommit 32d21757c1e4446cc87ddb2e93c4d49c0d205eb3\nMerge: e618ad9 e60e9b9\nAuthor: sergeypdev <sergeypoznyak@protonmail.com>\nDate:   Fri Jan 10 01:29:33 2025 +0400\n\n    Merge commit 'e60e9b99af9e2738378444265819df71c8bba134' as 'libs/tracy'\n=====\n\n\nI tried doing a fresh clone of the repo, but the exact same issue persists. You can reproduce yourself if you want, the repo is public: https://git.sergeyp.dev/sergeypdev/gutter_runner\n\n\nI'm using\nGit Version: 2.50.1\nOS: Fedora Workstation 41\n\n\n\nThank you,\nSergei.\n"}]}