From: "Tuncer Ayaz" <tuncer.ayaz@gmail.com>
To: "Tim Bird" <tim.bird@am.sony.com>
Cc: "linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Problem with http URL for stable git tree?
Date: Tue, 5 Jun 2007 08:16:52 +0200 [thread overview]
Message-ID: <4ac8254d0706042316n2b78f7b1y5ed81da50b148e7a@mail.gmail.com> (raw)
In-Reply-To: <466488C6.3070100@am.sony.com>
On 6/4/07, Tim Bird <tim.bird@am.sony.com> wrote:
> Greg KH wrote:
> > On Mon, Jun 04, 2007 at 12:10:01PM -0700, Tim Bird wrote:
> >> Greg,
> >>
> >> I'm having problems cloning the stable git tree for 2.6.21.
> >> Here's what I get:
> >>
> >> $ git clone http://www.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.21.y.git stable-2.6.21.y
> >> Cannot get remote repository information.
> >> Perhaps git-update-server-info needs to be run there?
> >
> > Ick, don't clone by "http://", please use the git protocol instead:
> > git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-2.6.21.y.git
> >
> > that should work better.
>
> I'm behind a firewall that doesn't allow it. Luckily, the
> firewall has some holes to allow me ssh access to a few
> external machines. It looks like I can use a "git:" url on a
> box outside the firewall, then clone that to inside Sony
> with a "git+ssh:" url.
>
> I'll do that, unless someone else has a better suggestion.
> Pushes and pulls will be two steps each, but at least it works.
if you have :22 outbound access you could try git+ssh on git.kernel.org.
I guess you don't have :22 outbound open, do you?
next prev parent reply other threads:[~2007-06-05 6:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-04 19:10 Tim Bird
2007-06-04 21:13 ` Greg KH
2007-06-04 21:48 ` Tim Bird
2007-06-05 6:16 ` Tuncer Ayaz [this message]
2007-06-13 20:34 ` Phillip Susi
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=4ac8254d0706042316n2b78f7b1y5ed81da50b148e7a@mail.gmail.com \
--to=tuncer.ayaz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@am.sony.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
all inboxes | Powered by JetHome®