From: Charles Brossollet <chbrosso@lltech.fr>
To: git@vger.kernel.org
Subject: Re: Submodule status inside nested submodule fails
Date: Fri, 24 Feb 2012 13:41:35 +0000 (UTC) [thread overview]
Message-ID: <loom.20120224T142455-253@post.gmane.org> (raw)
In-Reply-To: loom.20120224T104003-230@post.gmane.org
Charles Brossollet <chbrosso <at> lltech.fr> writes:
> Searching for message in git source I found the test triggering the message to
> be an empty result for "git rev-parse --show-cdup". Running the command in
> ext/submodule strangely returns the *absolute* path of ext/submodule, which
> should not happen because this command returns path of current dir relative to
> the containing working tree.
Things are OK if I run the commands from Windows' CMD, but it fails when run in
MinGW shell, so I believe the problem is related to MsysGit, discussion follows
up on their list.
next prev parent reply other threads:[~2012-02-24 13:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 9:53 Submodule status inside nested submodule fails Charles Brossollet
2012-02-24 13:41 ` Charles Brossollet [this message]
2012-05-08 18:11 ` rollinsdr
2012-05-09 21:34 ` Heiko Voigt
2012-05-10 1:40 ` rollinsdr
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=loom.20120224T142455-253@post.gmane.org \
--to=chbrosso@lltech.fr \
--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 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).