On Tue Mar 16, 2021 at 5:23 PM EDT, Jeff King wrote: > - one of the advantages of straight http:// URLs is that they can > accessed by multiple tools. Most "forge" tools let you use the same > URL both for getting a human-readable page in a browser, as well as > accessing the repository with the Git CLI. I'd hate to see https+git > URLs become common, because they add friction there (though simply > supporting them at all gives people the choice of whether to use > them). I think their main use-cases would be limited to places where the distinction is necessary, such as for those packaging or CI tools. I don't expect us to end up in a situation where users are passing each other git+https URLs in everyday conversation. > - I'm also sympathetic to brian's point that there's a wider > ecosystem. It's not just "git" that needs to learn them. It's jgit, > and libgit2, and many tools that work with git remotes. I would be happy to write the necessary patch for libgit2, at least.
