From: Benjamin Shropshire <benjamin.shropshire@economicmodeling.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
Benjamin Shropshire <benjamin.shropshire@economicmodeling.com>,
git@vger.kernel.org
Subject: Re: Relative url values in .gitmodules confusingly sensitive to clone via ssh vs https.
Date: Mon, 23 Mar 2020 08:09:39 -0700 [thread overview]
Message-ID: <CAAjm7GZXNXcGMp7p2f+UoDUWMPY+Z4aFHv35tynteVSKDf2Fqw@mail.gmail.com> (raw)
In-Reply-To: <20200323011117.GC6499@camp.crustytoothpaste.net>
$ git --version
git version 2.20.1
On Sun, Mar 22, 2020 at 6:11 PM brian m. carlson
<sandals@crustytoothpaste.net> wrote:
>
> On 2020-03-17 at 18:34:09, Benjamin Shropshire wrote:
> > From my perspective, this is a bug.
> >
> > If I clone a repo twice like this:
> >
> > git clone https://github.com/user/repo.git ./https
> > git clone git@github.com:user/repo.git ./ssh
> >
> > And if it contains a .gitmodules like this:
> >
> > [submodule "x"]
> > path = xxx
> > url = ../../different-user/something.git
> >
> > When I `git submodule update --init --recursive` in each, only the
> > HTTPS version works. the SSH version confusingly seems to try to find
> > something at ~/different-user/something.git or some other path in the
> > local file system.
>
> What version of Git are you using? This works fine for me on a recent
> next. In addition, I see we have tests for this in t0060, and adding an
> additional case for this appears to pass.
> --
> brian m. carlson: Houston, Texas, US
> OpenPGP: https://keybase.io/bk2204
next prev parent reply other threads:[~2020-03-23 15:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 18:34 Relative url values in .gitmodules confusingly sensitive to clone via ssh vs https Benjamin Shropshire
2020-03-18 0:26 ` brian m. carlson
2020-03-18 16:02 ` Benjamin Shropshire
2020-03-20 1:18 ` brian m. carlson
2020-03-23 1:11 ` brian m. carlson
2020-03-23 15:09 ` Benjamin Shropshire [this message]
2020-03-23 23:53 ` brian m. carlson
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAAjm7GZXNXcGMp7p2f+UoDUWMPY+Z4aFHv35tynteVSKDf2Fqw@mail.gmail.com \
--to=benjamin.shropshire@economicmodeling.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).