Hello, Git (I have version 1.6.1.3) seems to misbehave when it comes to git submodule add and ./. Here is an example. ================================================ $ cd Configs $ git submodule add git@xxxxxxxxxxxxxxxxxxxxxxxx:obvious.git ./awesome/obvious Initialized empty Git repository in /home/garoth/Configs/awesome/obvious/.git/ stdin: is not a tty remote: Counting objects: 32, done. remote: Compressing objects: 100% (29/29), done. Receiving objects: 100% (32/32), 5.10 KiB, done. remote: Total 32 (delta 8), reused 0 (delta 0) Resolving deltas: 100% (8/8), done. $ git submodule init No submodule mapping found in .gitmodules for path 'awesome/obvious' $ git commit -m "Added obvious submodule" $ cd ~/Desktop $ git clone ~/Configs $ git submodule init No submodule mapping found in .gitmodules for path 'awesome/obvious' ================================================ Note how when I did git submodule add, I used ./awesome/obvious. The behaviour of "No submodule mapping found in .gitmodules for path 'awesome/obvious'" only occurs when you use ./. If I were to use: $ git submodule add git@xxxxxxxxxxxxxxxxxxxxxxxx:obvious.git awesome/obvious instead, then git handles everything just fine. Thanks to dsal in #git for helping me figure this out. Perhaps there is an error with regards to how the .gitmodules file is parsed or encoded. I'm not really a git developer, but I wanted to have this issue documented at least somewhere. Thanks, -Andrei Thorp -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
