Hi Andreas, El vie, 27-10-2017 a las 14:33 +0200, Andreas Schwab escribió: > 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://g > > ithu > > 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. Ok, I have understood that reading the git code but, is it possible to create this pipe using command line? Or is that something designed to be used inside the git execution? Thanks! > > Andreas. > -- Alvaro del Castillo San Félix acs@xxxxxxxxxxxx - Chief Technical Officer (CTO) http://www.bitergia.com "Software metrics for your peace of mind"
