From: "H. Peter Anvin" <hpa@zytor.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [git failure] failure pulling latest Linus tree
Date: Wed, 25 Oct 2006 10:36:54 -0700 [thread overview]
Message-ID: <453FA0B6.4040403@zytor.com> (raw)
In-Reply-To: <7v3b9ce1tk.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> "H. Peter Anvin" <hpa@zytor.com> writes:
>
>> 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.
>
> Would kernel.org prefer RPM cut on a FC6 box now?
>
No; since we have now (finally) archieved "OS parity" we're going to
keep hera, zeus1, and zeus2 in sync going forward.
>> 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.
>
> If that is git-daemon dying when talking to older clients, that
> has been fixed in 1.4.3.2 (it's virtual hosting support had an
> off-by-one wrong check to tell older clients from newer one).
>
> Sorry about that -- we heard about the incompatibility this
> Monday.
This stuff happens... it's dealt with now.
-hpa
next prev parent reply other threads:[~2006-10-25 17:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 9:12 [git failure] failure pulling latest Linus tree 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-25 16:13 ` Petr Baudis
2006-10-25 17:12 ` H. Peter Anvin
2006-10-25 17:35 ` Junio C Hamano
2006-10-25 17:36 ` H. Peter Anvin [this message]
2006-10-26 5:34 ` Oleg Verych
[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=453FA0B6.4040403@zytor.com \
--to=hpa@zytor.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.