git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tay Ray Chuan <rctay89@gmail.com>
To: Tim Michelsen <timmichelsen@gmx-topmail.de>
Cc: git@vger.kernel.org
Subject: Re: how to clone from github behindd a proxy?
Date: Thu, 21 Jan 2010 08:54:27 +0800	[thread overview]
Message-ID: <be6fef0d1001201654s78ba4e95r59754dd2645f587@mail.gmail.com> (raw)
In-Reply-To: <loom.20100120T102323-689@post.gmane.org>

Hi,

On Wed, Jan 20, 2010 at 5:29 PM, Tim Michelsen
<timmichelsen@gmx-topmail.de> wrote:
> git clone http://github.com/rwl/traitsbackendpyjamas
> Initialized empty Git repository in D:\sourcecode/traitsbackendpyjamas/.git/
> * Couldn't find host github.com in the _netrc file; using defaults
> * About to connect() to proxy proxy.example.com on port 8000 (#0)
> *   Trying 149.233.100.7... * Connected to proxy.example.com (149.233.100.7)
> port 8000 (#0)
>  GET http://github.com/rwl/traitsbackendpyjamas/info/refs HTTP/1.1
> User-Agent: git/1.6.5.1.1366.g8ed9
> Host: github.com
> Accept: */*
> Proxy-Connection: Keep-Alive
> Pragma: no-cache
>
> * The requested URL returned error: 404
> * Closing connection #0
> fatal: http://github.com/rwl/traitsbackendpyjamas/info/refs not found: did you
> run git update-server-info on the server?

this isn't a problem with your proxy - git connects to your proxy fine.

The problem is that the info/refs file isn't found at the repo URL you
specified.

I think for github repos, you need to put a ".git" behind the url, so
you should try cloning from

  http://github.com/rwl/traitsbackendpyjamas.git

instead.

-- 
Cheers,
Ray Chuan

      reply	other threads:[~2010-01-21  1:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20  9:29 how to clone from github behindd a proxy? Tim Michelsen
2010-01-21  0:54 ` Tay Ray Chuan [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=be6fef0d1001201654s78ba4e95r59754dd2645f587@mail.gmail.com \
    --to=rctay89@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=timmichelsen@gmx-topmail.de \
    /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).