From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Benjamin Shropshire <benjamin.shropshire@economicmodeling.com>
Cc: git@vger.kernel.org
Subject: Re: Relative url values in .gitmodules confusingly sensitive to clone via ssh vs https.
Date: Mon, 23 Mar 2020 23:53:58 +0000 [thread overview]
Message-ID: <20200323235358.GF6499@camp.crustytoothpaste.net> (raw)
In-Reply-To: <CAAjm7GZXNXcGMp7p2f+UoDUWMPY+Z4aFHv35tynteVSKDf2Fqw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 998 bytes --]
On 2020-03-23 at 15:09:39, Benjamin Shropshire wrote:
> $ git --version
> git version 2.20.1
Hmmm, it looks like that version has the same test, t0060, which has
this:
test_submodule_relative_url "(null)" "user@host:path/to/repo" "../subrepo" "user@host:path/to/subrepo"
test_submodule_relative_url "(null)" "user@host:repo" "../subrepo" "user@host:subrepo"
test_submodule_relative_url "(null)" "user@host:repo" "../../subrepo" ".:subrepo"
I have confirmed that your test case does work for me on the version of
Git I mentioned above with the following repos:
bmc@castro:foo/foo.git
bmc@castro:bar/bar.git
And foo.git having the following .gitmodules:
[submodule "bar.git"]
path = bar.git
url = ../../bar/bar.git
It's puzzling to me that this isn't working for you on 2.20.1 but it
works for me on a 2.26 prerelease, yet both versions have the same test.
--
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2020-03-23 23:54 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
2020-03-23 23:53 ` brian m. carlson [this message]
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=20200323235358.GF6499@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=benjamin.shropshire@economicmodeling.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.
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).