Regarding the depreciation of ssh+git/git+ssh protocols

c05186cc38ca4605bff1f275619d7d0faeaf2fa5 introduced ssh+git, and 07c7782cc8e1f37c7255dfc69c5d0e3f4d4d728c admitted this was a mistake. I argue that it was not a mistake.

The main use-case for the git-specific protocol is to disambiguate with other version control systems which also use SSH (or HTTPS), such as Mercurial, or simply downloading a tarball over HTTP.

Some things that are affected by this include package manager source lists and configurations for CI tooling (the latter being my main interest in this).

A lot of software already recognizes ssh+git or https+git for this purpose, and in the latter case, rewrites it to https before handing it off to git.

I would like to see this feature un-disowned, and https+git support added as well.