From: Justin Spahr-Summers <justin.spahrsummers@gmail.com>
To: git@vger.kernel.org
Subject: Bug: Recursive submodules fail when the repo path contains spaces
Date: Tue, 24 Jul 2012 12:01:30 -0700 [thread overview]
Message-ID: <1CE02EC2D88646D48EE7B7D71AD36234@gmail.com> (raw)
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.
--
Justin Spahr-Summers
next reply other threads:[~2012-07-24 19:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 19:01 Justin Spahr-Summers [this message]
2012-07-24 20:08 ` Bug: Recursive submodules fail when the repo path contains spaces Jens Lehmann
2012-07-24 20:26 ` Junio C Hamano
2012-07-24 20:33 ` Justin Spahr-Summers
2012-07-24 20:37 ` Junio C Hamano
2012-07-28 16:21 ` Heiko Voigt
2012-07-28 17:53 ` Justin Spahr-Summers
2012-07-29 18:31 ` Phil Hord
2012-07-29 19:30 ` Justin Spahr-Summers
2012-07-29 21:10 ` Phil Hord
2012-07-29 21:13 ` Justin Spahr-Summers
2012-07-24 20:30 ` Justin Spahr-Summers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1CE02EC2D88646D48EE7B7D71AD36234@gmail.com \
--to=justin.spahrsummers@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.