From: Jarek Poplawski <jarkao2@gmail.com>
To: Rami Rosen <roszenrami@gmail.com>
Cc: Netdev <netdev@vger.kernel.org>
Subject: Re: Net-next-2.6 and net-2.6 repos and git-cloning via http
Date: Tue, 15 Dec 2009 13:42:43 +0000 [thread overview]
Message-ID: <20091215134243.GA9276@ff.dom.local> (raw)
In-Reply-To: <b25312890912150204n1ee8e303xe1d165bd90c7c08c@mail.gmail.com>
On 15-12-2009 11:04, Rami Rosen wrote:
> Hello,
> Do the net-next-2.6 and net-2.6 repossupport git-clone via http (for
> cases when git port, 9418, is blocked ?)
David responded a similar question recently - http is not supported.
Jarek P.
>
> I am trying:
> git-clone http://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6.git
> Initialized empty Git repository in /home/rami/new/net-next-2.6/.git/
> fatal: http://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6.git/info/refs
> not found: did you run git update-server-info on the server?
>
> also:
> git-clone http://www.kernel.org/pub/scm/linux/kernel/git/davem/net-next-2.6.git
> Initialized empty Git repository in /home/rami/new/net-next-2.6/.git/
> gives the same result.
>
> (I just want to add that on some other repos, the info/refs does exist,
> for example, http://www.kernel.org/pub/scm/virt/kvm/pcbios.git/info/refs,
> and I can do git-clone with
> http with them, but I really don't know whether this is the reason or
> just a wild speculation).
>
> Rgs,
> Rami
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2009-12-15 13:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-15 10:04 Net-next-2.6 and net-2.6 repos and git-cloning via http Rami Rosen
2009-12-15 13:42 ` Jarek Poplawski [this message]
2009-12-15 19:49 ` Jarek Poplawski
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091215134243.GA9276@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=roszenrami@gmail.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.
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 NNTP newsgroup(s).