From: Justin Spahr-Summers <justin.spahrsummers@gmail.com>
To: Phil Hord <phil.hord@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Jens Lehmann <Jens.Lehmann@web.de>,
Heiko Voigt <hvoigt@hvoigt.net>
Subject: Re: Bug: Recursive submodules fail when the repo path contains spaces
Date: Sun, 29 Jul 2012 14:13:55 -0700 [thread overview]
Message-ID: <72E23CD93B354FB28AFD12DDA7303016@gmail.com> (raw)
In-Reply-To: <CABURp0oHchc8KuwE+AxwzygLSi30+qiyqX=tfj9_rQrjBgO5AA@mail.gmail.com>
On Sunday, 29. July 2012 at 14:10, Phil Hord wrote:
> On Sun, Jul 29, 2012 at 3:30 PM, Justin Spahr-Summers
> <justin.spahrsummers@gmail.com (mailto:justin.spahrsummers@gmail.com)> wrote:
> > Hmm, you're right. After further investigation, this actually looks like a weird issue with soft links. Here's some exact output (with spacing only for clarity), using a public test repository at https://github.com/jspahrsummers/recursive-submodules-test:
>
>
>
> I can reproduce the problem now on 1.7.10.3. However the problem goes
> away in 1.7.12 since it was fixed in
>
> 6eafa6d096ce6b0ae20e4c0fbb248958559daf64
> Author: Jens Lehmann <Jens.Lehmann@web.de (http://web.de)>
> Date: Thu Jul 12 19:45:32 2012 +0200
> Subject: submodules: don't stumble over symbolic links when cloning recursively
>
> Regards,
> Phil
Ah, good to know. Thanks, everyone, for the help.
next prev parent reply other threads:[~2012-07-29 21:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 19:01 Bug: Recursive submodules fail when the repo path contains spaces Justin Spahr-Summers
2012-07-24 20:08 ` 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 [this message]
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=72E23CD93B354FB28AFD12DDA7303016@gmail.com \
--to=justin.spahrsummers@gmail.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hvoigt@hvoigt.net \
--cc=phil.hord@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).