From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jiri Slaby <jirislaby@gmail.com>
Subject: Re: linux-next: limits tree fetch failure
Date: Mon, 09 Nov 2009 09:02:19 +0100
Message-ID: <4AF7CC8B.2080400@gmail.com>
References: <20091109103017.6099f588.sfr@canb.auug.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: 7bit
Return-path: <linux-next-owner@vger.kernel.org>
Received: from mail-fx0-f221.google.com ([209.85.220.221]:62986 "EHLO
	mail-fx0-f221.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1753501AbZKIICS (ORCPT
	<rfc822;linux-next@vger.kernel.org>); Mon, 9 Nov 2009 03:02:18 -0500
In-Reply-To: <20091109103017.6099f588.sfr@canb.auug.org.au>
Sender: linux-next-owner@vger.kernel.org
List-ID: <linux-next.vger.kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org

On 11/09/2009 12:30 AM, Stephen Rothwell wrote:
> Today's linux-next fetch of the limits tree produced this error:
> 
> decibel.fi.muni.cz[0: 147.251.50.163]: errno=Connection timed out
> fatal: unable to connect a socket (Connection timed out)

Hi, ah, power outages and electricity reconnections. It's up and running
now. Thanks.