From: Larry Finger <Larry.Finger@lwfinger.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Michael Buesch <mb@bu3sch.de>,
netdev@vger.kernel.org, Daniel Drake <dsd@gentoo.org>
Subject: Re: wireless-2.6 git repos broken
Date: Mon, 24 Jul 2006 19:17:43 -0500 [thread overview]
Message-ID: <44C56327.2010000@lwfinger.net> (raw)
In-Reply-To: <20060724161441.GA17005@tuxdriver.com>
John W. Linville wrote:
> On Sun, Jul 23, 2006 at 11:13:52AM -0500, Larry Finger wrote:
>> Michael Buesch wrote:
>>> On Sunday 23 July 2006 17:59, Larry Finger wrote:
>>>>> Do you have the same problem on other git trees?
>>>>> I saw some people running into this error when cloning Linus'
>>>>> linux-2.6.git. I couldn't reproduce it, using exactly the same git
>>>>> version.
>>>> I had the same error when pulling from Linus's tree. It was fixed with a
>>>> 'git fsck-objects --full' command.
>>> Uhm, that tells me the git tree on kernel.org is broken
>>> and John has to run this command, right?
>>>
>> I think so.
>
> Hmmm...well, I'll look into it. FWIW, I cloned my git tree from
> kernel.org onto my laptop while I was at OLS w/o any problems.
There is a thread today on LKML that says that the git server errors out (wrongly) if the download
does not finish in 10 minutes. That problem is being fixed, but they suggest using rsync protocol to
clone a large repository.
Michael, is this the cause of your problem?
Larry
prev parent reply other threads:[~2006-07-25 0:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-23 15:22 wireless-2.6 git repos broken Michael Buesch
2006-07-23 15:52 ` Daniel Drake
2006-07-23 15:59 ` Larry Finger
2006-07-23 16:07 ` Michael Buesch
2006-07-23 16:13 ` Larry Finger
2006-07-24 16:14 ` John W. Linville
2006-07-25 0:17 ` Larry Finger [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=44C56327.2010000@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=dsd@gentoo.org \
--cc=linville@tuxdriver.com \
--cc=mb@bu3sch.de \
--cc=netdev@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.
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).