git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: "Aubrey Li" <aubreylee@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git clone problem through HTTP
Date: Fri, 20 Apr 2007 14:09:35 -0700	[thread overview]
Message-ID: <7vk5w6ycq8.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <7vodliyd1j.fsf@assigned-by-dhcp.cox.net> (Junio C. Hamano's message of "Fri, 20 Apr 2007 14:02:48 -0700")

Junio C Hamano <junkio@cox.net> writes:

> "Aubrey Li" <aubreylee@gmail.com> writes:
>
>> 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. I've tried
>>
>> git version 1.4.4.2
>> git version 1.4.4.4
>> git version 1.5.0.1
>> git version 1.5.0.4
>> git version 1.5.0.6
>> git version 1.5.1.1,
>>
>> none of them work. The following is the error.
>
>         $ git init
>         $ git remote add origin http://.../linux-2.6.git

This step needs to have "add -m master" instead of just "add".

> 	$ git config branch.master.remote origin
> 	$ git config branch.master.merge refs/heads/master
>         $ git fetch
>         $ git merge origin

Otherwise you end up having to say "git merge origin/master" here.

>
> should work, because I knew about this problem and fixed it in
> git-fetch in v1.5.0.

  reply	other threads:[~2007-04-20 21:09 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
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 [this message]
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=7vk5w6ycq8.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=aubreylee@gmail.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).