From: Wang Chen <wangchen@cn.fujitsu.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@elte.hu>,
FNST-Lai Jiangshan <laijs@cn.fujitsu.com>,
FJ-KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
"H. Peter Anvin" <hpa@zytor.com>,
git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: tip tree clone fail
Date: Fri, 10 Oct 2008 16:57:38 +0800 [thread overview]
Message-ID: <48EF1902.4070309@cn.fujitsu.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0810101046260.3271@apollo>
Thomas Gleixner said the following on 2008-10-10 16:56:
> On Fri, 10 Oct 2008, Wang Chen wrote:
>> Thomas Gleixner said the following on 2008-10-10 16:40:
>>> On Fri, 10 Oct 2008, Ingo Molnar wrote:
>>>
>>>> Cc:-ed Thomas too - Thomas just ran a clean git clone and that succeeded
>>>> for him, both over the http and over the git protocols.
>>> No, I did ssh and git. Will start a http one now.
>> OK. I will wait.
>> Thanks, Thomas :)
>
> git clone http://www.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-tip.git
>
> fails here as well.
>
> Getting pack 7c461fa5d92f9e047ae07b70eb30828a63a803f5
> which contains 874e848aefc2d5952b00593c9fd23d748259eec7
> walk 874e848aefc2d5952b00593c9fd23d748259eec7
> Getting pack list for http://www.kernel.org/home/ftp/pub/scm/linux/kernel/git/torvalds/linux-2.6.git/
> Getting pack list for http://www.kernel.org/home/ftp/pub/scm/linux/kernel/git/sfr/linux-next.git/
> error: Unable to find 85ba94ba0592296053f7f2846812173424afe1cb under http://www.kernel.org/pub/scm/linux/kernel/git/x86/linux-2.6-tip.git
> Cannot obtain needed object 85ba94ba0592296053f7f2846812173424afe1cb
> while processing commit 874e848aefc2d5952b00593c9fd23d748259eec7.
> fatal: Fetch failed.
>
> The needed object 85ba94ba0592296053f7f2846812173424afe1cb is a commit
> in linus tree.
>
> So http transport is wreckaged. (git version 1.6.0.1 here, Wang is using
> 1.5.3.x)
>
My git version is 1.5.5.1, although it doesn't matter ;)
> Junio, can you please have a look ? I know it's http again, but we can
> not sanitze the corporate firewall folks by any means.
>
next prev parent reply other threads:[~2008-10-10 9:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <48EEA714.4010205@cn.fujitsu.com>
[not found] ` <20081010072951.GB16016@elte.hu>
[not found] ` <20081010083720.GA32069@elte.hu>
[not found] ` <alpine.LFD.2.00.0810101040200.3271@apollo>
[not found] ` <48EF14FC.1000801@cn.fujitsu.com>
2008-10-10 8:56 ` tip tree clone fail Thomas Gleixner
2008-10-10 8:57 ` Wang Chen [this message]
2008-10-10 15:58 ` H. Peter Anvin
2008-10-12 11:28 ` Wang Chen
2008-10-12 12:04 ` Lars Hjemli
2008-10-12 14:15 ` H. Peter Anvin
2008-10-12 12:41 ` Ingo Molnar
2008-10-12 12:59 ` Miklos Vajna
2008-10-12 14:14 ` H. Peter Anvin
2008-10-12 15:24 ` Ingo Molnar
2008-10-12 15:36 ` Teemu Likonen
2008-10-12 15:39 ` Petr Baudis
2008-10-12 16:59 ` Ingo Molnar
2008-10-12 17:37 ` Jakub Narebski
2008-10-12 17:59 ` Shawn O. Pearce
2008-10-13 4:09 ` H. Peter Anvin
2008-10-13 9:40 ` Wang Chen
2008-10-13 15:59 ` H. Peter Anvin
2008-10-15 3:43 ` Wang Chen
2008-10-15 5:25 ` H. Peter Anvin
2008-10-13 4:07 ` H. Peter Anvin
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=48EF1902.4070309@cn.fujitsu.com \
--to=wangchen@cn.fujitsu.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=hpa@zytor.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.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).