On Fri, Sep 11, 2015 at 05:15:52PM +0200, Jens Lehmann wrote: > Am 10.09.2015 um 22:06 schrieb Filip Gospodinov: > > I know that for this particular use case I can just use `git clone --recursive` > > and that other use cases can be worked around by using `cd`. Still, I wonder if > > the behavior I discovered is a bug or if it's expected. > > I don't think this is a bug. The git submodule command needs a work tree > to read the .gitmodules file from, that's while it fails when using > --git-dir from outside the work tree. But I admit that the error message > "No submodule mapping found in .gitmodules for path ..." could be improved > to clearly state that the .gitmodules file wasn't found. > > Unfortunately trying to show git the right work tree: > > $ git --git-dir=$PWD/repo2/.git --work-tree=$PWD/repo2 submodule update --init > > Didn't work as I expected it to either: > > fatal: /home/Sledge/libexec/git-core/git-submodule cannot be used without a working tree. > > So you'll have to cd into the repo for now. There's also "git -C /path/to/repo" which avoids the need for a separate "cd". -- 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