On Okt 27 2017, Alvaro del Castillo <acs@xxxxxxxxxxxx> wrote: > We're wondering why "fetch-pack" (when is running from the command > line) doesn't handle "https://"; protocol. It only works with "git://". > > For instance, this doesn't work: > > $ git fetch-pack https://github.com/git/git refs/heads/master > fatal: I don't handle protocol 'https' > > while this does: > > $ git fetch-pack git://github.com/git/git refs/heads/master > > The funny thing is that under the hood, "fetch" calls "fetch-pack" > using "https" procotol. Example of a trace below: > > 12:03:07.512558 git.c:344 trace: built-in: git 'fetch- > pack' '--stateless-rpc' '--stdin' '--lock-pack' '--thin' 'https://githu > b.com/git/git/' With --stateless-rpc, fetch-pack doesn't do the connect itself, but expects the caller having set up a pipe to it. The URL is then actually ignored. Andreas. -- Andreas Schwab, schwab@xxxxxxxxxxxxxx GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
