Am 03.02.2013 23:36, schrieb TJ: > I've recently had need to re-arrange more than ten submodules within a > project and discovered there is apparently no easy way to do it. > > Using some suggestions I found on Stack Overflow I eventually figured out the > steps required. Because the steps can be > complex I thought it would be handy to have a tool to automate the > functionality. > > I have put together a reasonably bullet-proof shell script > "git-submodule-move" that does the job pretty well. I've put it through quite > a bit of testing and trusted it with my own project and it has > performed well. > > I've published to github so others can use and improve it. > > https://github.com/iam-TJ/git-submodule-move
I'd propose to drop these two steps: updating super-repository's submodule name moving super-repository's submodule repository Changing the name makes the moved submodule a completely new entity and will lead to a reclone of the repository as soon as recursive checkout materializes. And Trevor already mentioned the long term solution which is to teach "git mv" to do all that, which is next on my list. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
