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

state of the art with moving submodules

From
Chris Packham <judge.packham@gmail.com>
Date
Feb 26, 2013, 08:09 UTC
Message-ID
<512C6DD2.4000208@gmail.com>
In-Reply-To
<bcaec55555fe91182f04d698b37f@google.com>
Hi Jens,
(sorry for the dup. gmail insists on sending html)

I know I saw a few threads regarding support for moving submodules but I lost track of the discussion.

At $dayjob we were discussing a potential re-org of our super-projects to introduce a bit of hierarchy to the submodules (at the moment it's fairly flat). One downside of this is the potential loss of locally committed work. There is also a cost in terms of additional fetching but we think that will be OK (fetches from local servers with smallish repos).

I was just wondering where things were at with git detecting submodule moving/renaming? Will our developers be able to keep any local commits when they happen to pull in the super-project commit that moves a commit.

I think some people with older clones will suffer without the newer .git/modules layout but those can be manually fixed prior to the re-org.

FYI our current stock workstation install uses git version 1.7.9.5 but I'm recommending we update to 1.8.x before this re-org to pick up some of the recent submodule improvements.

Thanks Chris

Next: Jens Lehmann
Message 1 of 2 in “state of the art with moving submodules”
  1. Chris PackhamFeb 26, 2013
  2. Jens LehmannFeb 26, 2013

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.