From: Junio C Hamano <gitster@pobox.com>
To: Mark Lodato <lodato@google.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Eli Schwartz <eschwartz@archlinux.org>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Drew DeVault <sir@cmpwn.com>,
git@vger.kernel.org
Subject: Re: Regarding the depreciation of ssh+git/git+ssh protocols
Date: Wed, 07 Apr 2021 12:46:56 -0700 [thread overview]
Message-ID: <xmqqv98xzxlb.fsf@gitster.g> (raw)
In-Reply-To: <20210407134646.2866522-1-lodato@google.com> (Mark Lodato's message of "Wed, 7 Apr 2021 09:46:46 -0400")
Mark Lodato <lodato@google.com> writes:
> The common thread is that systems need a way to uniquely identify a git
> repository or some object therein. I believe this means some combination
> of:
>
> - VCS type (git)
> - Transport location (e.g. https://github.com/git/git)
> - Ref (e.g. master)
> - Resolved commit ID (e.g. 48bf2fa8bad054d66bd79c6ba903c89c704201f7)
> - Path (e.g. contrib/diff-highlight)
> - (possibly) Clone depth
Nice. So there is no reason to expect that these downstream systems
can sanely force various VCS systems that the notation they use for
"transport location" would identify what VCS type uses that
location. All the other details (like refs, which may other VCS
many not even have) other than VCS type depend on the VCS used.
Thanks.
next prev parent reply other threads:[~2021-04-07 19:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 16:27 Regarding the depreciation of ssh+git/git+ssh protocols Drew DeVault
2021-03-15 17:56 ` Jonathan Nieder
2021-03-15 18:14 ` Drew DeVault
2021-03-15 22:01 ` brian m. carlson
2021-03-16 0:52 ` Drew DeVault
2021-03-16 1:02 ` Jonathan Nieder
2021-03-16 1:05 ` Drew DeVault
2021-03-16 21:23 ` Jeff King
2021-03-17 14:49 ` Drew DeVault
2021-03-18 21:30 ` Junio C Hamano
2021-03-18 21:53 ` Drew DeVault
2021-03-16 4:38 ` Eli Schwartz
2021-03-16 11:54 ` brian m. carlson
2021-03-16 14:21 ` Drew DeVault
2021-03-16 21:28 ` Jeff King
2021-03-17 14:50 ` Drew DeVault
2021-03-17 0:45 ` Jakub Narębski
2021-03-17 14:53 ` Drew DeVault
2021-03-17 22:06 ` brian m. carlson
2021-03-18 12:53 ` Drew DeVault
2021-03-16 18:03 ` Eli Schwartz
2021-03-17 22:15 ` Jonathan Nieder
2021-03-31 4:23 ` Eli Schwartz
2021-04-07 13:46 ` Mark Lodato
2021-04-07 19:46 ` Junio C Hamano [this message]
2021-04-13 8:52 ` Kerry, Richard
2021-03-16 0:54 ` Drew DeVault
-- strict thread matches above, loose matches on Subject: below --
2023-10-13 20:49 David Rogers
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=xmqqv98xzxlb.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=eschwartz@archlinux.org \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=lodato@google.com \
--cc=sandals@crustytoothpaste.net \
--cc=sir@cmpwn.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.
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).