From: Alvaro del Castillo <acs@bitergia.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: git@vger.kernel.org, sduenas@bitergia.com
Subject: Re: Why does fetch-pack not works over http?
Date: Mon, 30 Oct 2017 17:58:13 +0100 [thread overview]
Message-ID: <1509382693.27976.15.camel@bitergia.com> (raw)
In-Reply-To: <873764bwjd.fsf@linux-m68k.org>
Hi Andreas,
El vie, 27-10-2017 a las 14:33 +0200, Andreas Schwab escribió:
> On Okt 27 2017, Alvaro del Castillo <acs@bitergia.com> 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@bitergia.com - Chief Technical Officer (CTO)
http://www.bitergia.com
"Software metrics for your peace of mind"
prev parent reply other threads:[~2017-10-30 16:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 10:42 Why does fetch-pack not works over http? Alvaro del Castillo
2017-10-27 12:33 ` Andreas Schwab
2017-10-30 16:58 ` Alvaro del Castillo [this message]
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=1509382693.27976.15.camel@bitergia.com \
--to=acs@bitergia.com \
--cc=git@vger.kernel.org \
--cc=schwab@linux-m68k.org \
--cc=sduenas@bitergia.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).