git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Bug: Recursive submodules fail when the repo path contains spaces

From
Justin Spahr-Summers <justin.spahrsummers@gmail.com>
Date
Jul 24, 2012, 20:30 UTC
Message-ID
<D842C9D621F44E398A1145EC1B67580C@gmail.com>
In-Reply-To
<500F00C7.4040209@web.de>
On Tuesday, 24. July 2012 at 13:08, Jens Lehmann wrote:
Show 18 quoted lines
> Am 24.07.2012 21:01, schrieb Justin Spahr-Summers:
> > 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?  
The only test that fails is:  

*** t7501-commit.sh *** *** t7502-commit.sh *** … not ok - 13 commit message from template with whitespace issue

(which I assume is unrelated)
Previous: Justin Spahr-Summers
Message 12 of 12 in “Bug: Recursive submodules fail when the repo path contains spaces”
  1. Justin Spahr-SummersJul 24, 2012
  2. Jens LehmannJul 24, 2012
  3. Junio C HamanoJul 24, 2012
  4. Justin Spahr-SummersJul 24, 2012
  5. Junio C HamanoJul 24, 2012
  6. Heiko VoigtJul 28, 2012
  7. Justin Spahr-SummersJul 28, 2012
  8. Phil HordJul 29, 2012
  9. Justin Spahr-SummersJul 29, 2012
  10. Phil HordJul 29, 2012
  11. Justin Spahr-SummersJul 29, 2012
  12. Justin Spahr-SummersJul 24, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.