{"thread":{"id":"60901","subject":"Bug: git-subtree: splitting subtree fails when subtree was added, removed and added again","startedAt":"2024-02-11T20:16:54Z","lastAt":"2024-02-11T20:16:54Z","messageCount":1,"participants":["tionis"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"488418","messageId":"1d8fa22c-eb13-4cdb-8499-e19f0dea6b42@tionis.dev","threadId":"60901","inReplyTo":null,"subject":"Bug: git-subtree: splitting subtree fails when subtree was added, removed and added again","fromName":"tionis","fromEmail":"git@tionis.dev","sentAt":"2024-02-11T20:16:47Z","receivedAt":"2024-02-11T20:16:54Z","isPatch":false,"sender":{"key":"git@tionis.dev","avatar":null},"body":"I discovered a problem in git-subtree that I could also reproduce in a \nminimal proof of concept over at\nhttps://github.com/tionis/git-subtree-bug-poc\n\nThe same bug was discussed some time ago on stackoverflow: \nhttps://stackoverflow.com/questions/68761778/git-subtree-cache-exists\n\nIt seems to occur when a subtree was added, removed, alter added again \nand then modified in some commit.\n\nThis leads to some error with the cache leading to an error message like\n\nfatal: cache for $commit-hash-here already exists!\n\nI'm unsure how to work around this other than modify the history or \ncreating a branch from before the first addition and fixing it there.\n"}]}