{"thread":{"id":"54445","subject":"question on \"git subtree split\"","startedAt":"2020-10-16T22:50:06Z","lastAt":"2020-10-16T22:50:06Z","messageCount":1,"participants":["Erwin Dondorp"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"407771","messageId":"a21e69ca-4a44-2d2f-339c-0b3f3fdd867a@ziggo.nl","threadId":"54445","inReplyTo":null,"subject":"question on \"git subtree split\"","fromName":"Erwin Dondorp","fromEmail":"erwindon@ziggo.nl","sentAt":"2020-10-16T22:31:29Z","receivedAt":"2020-10-16T22:50:06Z","isPatch":false,"sender":{"key":"erwindon@ziggo.nl","avatar":null},"body":"Hello,\n\nI'm splitting the directories of one large repository into multiple \nrepositories using \"git subtree split\".\nEverything is clear and understandable thanks to \nhttps://stackoverflow.com/questions/359424/detach-move-subdirectory-into-separate-git-repository#17864475\nThe new branch is created and contains exactly the expected commits.\n\nBut the oldest commit from the new branch is not connected to the \ninitial (empty) commit of the repository.\nInstead, it is a new parent-less commit.\nThis causes problems with some of the next operations that I need to \nperform as project cleanup, like squashing/re-ordering commits.\n\nIs this intentional that the oldest commit of the new branch is parent-less?\n\nErwin\n\n"}]}