From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1753867Ab1IFSQs (ORCPT <rfc822;w@1wt.eu>);
	Tue, 6 Sep 2011 14:16:48 -0400
Received: from oproxy4-pub.bluehost.com ([69.89.21.11]:60584 "HELO
	oproxy4-pub.bluehost.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with SMTP id S1753685Ab1IFSQn convert rfc822-to-8bit (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 6 Sep 2011 14:16:43 -0400
Date: Tue, 6 Sep 2011 10:37:18 -0700
From: Randy Dunlap <rdunlap@xenotime.net>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: Josh Boyer <jwboyer@gmail.com>, Stephen Rothwell <sfr@canb.auug.org.au>,
        linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: no tree for Sept 6
Message-Id: <20110906103718.2c57eb3e.rdunlap@xenotime.net>
In-Reply-To: <CACqU3MXQw4+QyBmCPcO8ZmYu0T6N+DStXBoa=JUv+ej6cWMTnw@mail.gmail.com>
References: <20110906164049.4dd3961cb82800b8d7cc8741@canb.auug.org.au>
	<CACqU3MXcZ72eYNd=duPYdR_gOe-ejnHoLSMqK_ZU3y=MR2-0+A@mail.gmail.com>
	<CA+5PVA7CETUa0i3U20ifz5YjXAywTGD2NEQt1GcJz1OwY_DtEg@mail.gmail.com>
	<CACqU3MXQw4+QyBmCPcO8ZmYu0T6N+DStXBoa=JUv+ej6cWMTnw@mail.gmail.com>
Organization: YPO4
X-Mailer: Sylpheed 2.7.1 (GTK+ 2.16.6; x86_64-unknown-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8BIT
X-Identified-User: {1807:box742.bluehost.com:xenotime:xenotime.net} {sentby:smtp auth 50.53.38.135 authed with rdunlap@xenotime.net}
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Tue, 6 Sep 2011 13:29:23 -0400 Arnaud Lacombe wrote:

> Hi,
> 
> On Tue, Sep 6, 2011 at 1:23 PM, Josh Boyer <jwboyer@gmail.com> wrote:
> > On Tue, Sep 6, 2011 at 1:17 PM, Arnaud Lacombe <lacombar@gmail.com> wrote:
> >> Hi,
> >>
> >> On Tue, Sep 6, 2011 at 2:40 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >>> Hi all,
> >>>
> >>> With master.kernel.org down, there is not much change from yesterday and
> >>> I cannot publish the resulting linux-next tree anyway, so there is no
> >>> tree today.
> >>>
> >> What about github ? gitorious ?
> >>
> >> If you fork linus' tree on github, you should still be within the disk
> >> usage limit. My linux-2.6-next.git bare tree mirror is about 303MB.
> >
> > Well... that would be helpful if all of the trees that linux-next
> > pulls from are hosted somewhere other than kernel.org as well.  A lot
> > of them are not, which means you would get an incomplete linux-next
> > tree at best.  Probably better to just wait.
> >
> That's just insane...
> 
> git is distributed, but still used centrally. Kernel development
> should just not be impacted by such issues.

Key word is "should," but reality intervenes.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***