git/list[1] front-page[2] threads[3] people[4] search[5] about
 

question on "git subtree split"

From
EDErwin Dondorp <erwindon@ziggo.nl>
Date
Oct 16, 2020, 22:31 UTC
Message-ID
<a21e69ca-4a44-2d2f-339c-0b3f3fdd867a@ziggo.nl>
Hello,

I'm splitting the directories of one large repository into multiple repositories using "git subtree split". Everything is clear and understandable thanks to https://stackoverflow.com/questions/359424/detach-move-subdirectory-into-separate-git-repository#17864475 The new branch is created and contains exactly the expected commits.

But the oldest commit from the new branch is not connected to the initial (empty) commit of the repository. Instead, it is a new parent-less commit. This causes problems with some of the next operations that I need to perform as project cleanup, like squashing/re-ordering commits.

Is this intentional that the oldest commit of the new branch is parent-less?
Erwin
Message 1 of 1 in “question on "git subtree split"”
  1. Erwin DondorpOct 16, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.