mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oleg Verych <olecom@flower.upol.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: [git failure] failure pulling latest Linus tree
Date: Thu, 26 Oct 2006 05:34:26 +0000 (UTC)	[thread overview]
Message-ID: <slrnek0iji.93p.olecom@flower.upol.cz> (raw)
In-Reply-To: <453F8630.2000608@zytor.com>

On 2006-10-25, H. Peter Anvin wrote:
> Linus Torvalds wrote:
>> 
>> On Wed, 25 Oct 2006, Jes Sorensen wrote:
>>> Known error? git tree corrupted or need for a new version of git?
>> 
>> For some reason, the mirroring seems to be really slow or broken to one of 
>> the public servers (zeus-pub1). It looks to be affecting gitweb too (ie 
>> www1.kernel.org is busted, while www2.kernel.org seems ok)
>> 
>
> For some reason which we haven't been able to track down yet, the recent 
> load imposed by FC6 caused zeus1's load to skyrocket, but not zeus2's... 
> it's largely a mystery.
>
> HOWEVER, git 1.4.3 seems to have been bad chicken.  When we ran it we 
> got a neverending stream of segfaults in the logs.

Please, are there more gitweb services of kernel.org's one?

I know this may be stupid as anyone can git clone && etc. But in my
case all i need (mostly) is history and logs (i've started my devel
from patches, and they are mirrored pretty good).

TIA.

-o--=O`C  /. .\
 #oo'L O      o
<___=E M    ^--


  reply	other threads:[~2006-10-26  5:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-25  9:12 Jes Sorensen
2006-10-25 10:18 ` Oleg Verych
2006-10-25 14:50 ` Linus Torvalds
2006-10-25 15:43   ` H. Peter Anvin
2006-10-26  5:34     ` Oleg Verych [this message]
     [not found]     ` <72AE9332-F318-4853-8DC9-B6BC7FD1E055@kernel.crashing.org>
2006-10-26 16:40       ` 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=slrnek0iji.93p.olecom@flower.upol.cz \
    --to=olecom@flower.upol.cz \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®