Nowadays there’s a much easier way to do it than manually using git filter-branch: git subtree Installation NOTE git-subtree is now part of git (if you install contrib) as of 1.7.11, so you might already have it installed. You may check by executing git subtree. To install git-subtree from source (for older versions of git): … Read more
If the location (URL) of the submodule has changed, then you can simply: Modify the .gitmodules file in the repo root to use the new URL. Delete the submodule folder in the repo rm -rf .git/modules/<submodule>. Delete the submodule folder in the working directory rm -rf <submodule>. Run git submodule sync. Run git submodule update. … Read more
Update 2020: The OP BartBog reports in the comments: The current (2016) answer does not work that well (anymore?) with subsubmodules since $top/.gitmodules does not contain the branch info of the subsub (and subsubsub modules) New solution: export top=$(pwd) git submodule foreach ‘b=$(git config -f ${top}/.gitmodules submodule.${path}.branch); \ case “${b}” in \ “”) git checkout … Read more
I end up there by searching how to update specific submodule only, which means for me, updating a submodule to the ref pointed by its super-repo. Which is not the question nor the answer but only the title. So in a hope of helping some others like me the answer to the question title is … Read more
Which is best for you depends on your needs, desires, and workflow. They are in some senses semi-isomorphic, it is just some are a lot easier to use than others for specific tasks. gitslave is useful when you control and develop on the subprojects at more of less the same time as the superproject, and … Read more
If manually editing the patch file is out of the question or infeasible, this can be done with standard options (available in git apply, git format-patch and GNU patch). -p<n> removes n leading directories from the paths in the patch. After processing -p, –directory=<root> prepends root to each of the paths in the patch before … Read more
As mentioned in Retrospectively add –recursive to a git repo git submodule update –init –recursive should work.
I’m afraid there’s not enough information in your question to be certain about what’s going on, since you haven’t replied to my follow-up question, but this may be of help in any case. That error means that projectfolder is already staged (“already exists in the index”). To find out what’s going on here, try to … Read more
Submodules are always checked out in a detached HEAD mode. That is because a submodule will checkout the SHA1 stored in the special entry in the index of the parent repo. Plus, if you want a submodule to follow the branch you have registered in the .gitmodules, you need: git submodule update –init –remote The … Read more
I figured out another solution which looks rather clean to me. Just give git all the info it needs to perform the submodule stuff: $ cd /path/to/your/git_work_tree $ git –git-dir=/path/to/your/bare_repo.git –work-tree=. submodule init $ git –git-dir=/path/to/your/bare_repo.git –work-tree=. submodule update