Re: Bug: Recursive submodules fail when the repo path contains spaces
- From
Jens Lehmann <jens.lehmann@web.de>
- Date
- Jul 24, 2012, 20:08 UTC
- Message-ID
- <500F00C7.4040209@web.de>
- In-Reply-To
- <1CE02EC2D88646D48EE7B7D71AD36234@gmail.com>
Am 24.07.2012 21:01, schrieb Justin Spahr-Summers:
Show 10 quoted lines
> This occurs on Mac OS X 10.7.4, on git versions 1.7.10.2 (Apple Git-33) and 1.7.11.3. > > Steps: > 1. Create or clone a repository to an absolute path that contains spaces. > 2. Add a submodule to the repository, if it does not already have one. > 3. Within that submodule, attempt to add another submodule. > > The result is an error "fatal: Not a git repository", followed by the relative path to the submodule directory within .git/modules of the top-level repository. > > Similarly, using "git submodule update --init --recursive" in a freshly-cloned repository that matches the above configuration will fail with the same error. "git clone --recursive" does not seem to suffer from the same problem at clone time, but will still fail to add recursive submodules.
Hmm, I don't understand how that is different from what t7407 does, it uses "git submodule update --init --recursive" in to populate recursive submodules in a freshly cloned repository whose path contains a space (in the trash directory name) in test number 8.
Does the git test suite succeed for you?