You can bind mount the submodule’s other directory sudo mount –bind /path/to/main/repo relative/path/to/submodule I can’t find much info about this method, but saw it listed in this, similar question.
This apparently is very much dependent on the version of git you are using. If present, change the url entry in the [submodule “<dirname>”] section of the .gitmodules file. If present, change the url entry in the [submodule “<dirname>”] section of the .git/config file. Change the url in the configuration of the submodule itself. The … Read more
Don’t conflate the path and the name of a submodule. You want to run git submodule add [email protected]:ironsand/cookbook-foo.git foo/ instead. For more details, see the git-submodule man page; the relevant git-submodule syntax here is git submodule [–name <name>] <repository> [<path>] where… <repository> is the URL of the new submodule’s origin repository. <path>, if specified, determines … Read more
When you want to pull a specific new module, you can use the following command: git submodule update –init local/path/to/submodule/folder If you wish to initialize all new submodules however. you can omit the path to the folder like so: git submodule update –init
Update 2017: as I mentioned in “see diff of commit on submodule in gitlab”, Git 2.11 (Nov. 2016) introduces git diff –submodule=diff Git 2.14 (Q3 2017) will improve that by recursing into nested submodules. See commit 5a52214 (04 May 2017) by Stefan Beller (stefanbeller). (Merged by Junio C Hamano — gitster — in commit a531ecf, … Read more
Does ../extern/Lib1 refer to a Git repository? If it does not, Git wouldn’t know how to have the Git repo URL to its .gitmodule Also, try: with the destination lib not already existing (even empty) with an absolute path instead of a relative path (you can use a relative one, but just in case, it … Read more
You need to do git submodule update –init –recursive. The problem here is the submodule C is never being initialized in the first place.
Git stores information about submodules in two places. The first is in a file called .gitmodules, which is checked in to the git repository. Changes to this file are what get propagated to other repositories. The other location is in .git/config, and it’s where git actually looks when performing most commands. So imagine you’ve worked … Read more
I think you need to relax the ‘no commit to submodule’ constraint. There are two options: Commit your submodule changes to a submodule branch. It is your team’s branch and it is where your team put your submodule changes. When somebody clones the super project and updates the submodule they get the content of your … Read more
You may want to try git subtree (alt link) instead. I’ve had a lot of luck with it, using both remote repos and clean (untied to master history) branches in my project.