git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Medve Emilian-EMMEDVE1" <Emilian.Medve@freescale.com>
To: <git@vger.kernel.org>
Subject: RE: git clone problem through HTTP
Date: Fri, 20 Apr 2007 06:01:18 -0700	[thread overview]
Message-ID: <598D5675D34BE349929AF5EDE9B03E27EA8476@az33exm24.fsl.freescale.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0704201245330.10595@reaper.quantumfyre.co.uk>

Hi Aubery,


If you have a SOCKS server somewhere you could use socksify to get a
clone with the git native protocol.


Cheers,
Emil.


-----Original Message-----
From: git-owner@vger.kernel.org [mailto:git-owner@vger.kernel.org] On
Behalf Of Julian Phillips
Sent: Friday, April 20, 2007 6:48 AM
To: Aubrey Li
Cc: git@vger.kernel.org
Subject: Re: git clone problem through HTTP

On Fri, 20 Apr 2007, Aubrey Li wrote:

> I'm behind of a firewall on which the git port is not permitted, so I
> can only use http protocol. Unfortunately, I can't clone linus' git
> tree at all.

Linus packs his refs, which means that currently you can't clone using 
http, with any version of git.

Try http://repo.or.cz/r/linux-2.6.git/ instead?  This appears to be a 
straight clone, but without packed refs.

-- 
Julian

  ---
Go out and tell a lie that will make the whole family proud of you.
 		-- Cadmus, to Pentheus, in "The Bacchae" by Euripides

  reply	other threads:[~2007-04-20 13:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-20  7:15 git clone problem through HTTP Aubrey Li
2007-04-20 11:48 ` Julian Phillips
2007-04-20 13:01   ` Medve Emilian-EMMEDVE1 [this message]
2007-04-20 13:38   ` Aubrey Li
2007-04-20 13:59     ` Alex Riesen
2007-04-20 14:01     ` Brian Gernhardt
2007-04-20 14:19       ` Julian Phillips
2007-04-20 21:02 ` Junio C Hamano
2007-04-20 21:09   ` Junio C Hamano
2007-04-20 21:31   ` Junio C Hamano
2007-04-22  5:10     ` Aubrey Li

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=598D5675D34BE349929AF5EDE9B03E27EA8476@az33exm24.fsl.freescale.net \
    --to=emilian.medve@freescale.com \
    --cc=git@vger.kernel.org \
    /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).