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
Date: Tue, 6 Sep 2011 10:37:18 -0700 [thread overview]
Message-ID: <20110906103718.2c57eb3e.rdunlap@xenotime.net> (raw)
In-Reply-To: <CACqU3MXQw4+QyBmCPcO8ZmYu0T6N+DStXBoa=JUv+ej6cWMTnw@mail.gmail.com>
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 ***
next prev parent reply other threads:[~2011-09-06 17:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-06 6:40 linux-next: no tree for Sept 6 Stephen Rothwell
2011-09-06 17:17 ` Arnaud Lacombe
2011-09-06 17:23 ` Josh Boyer
2011-09-06 17:29 ` Arnaud Lacombe
2011-09-06 17:37 ` Randy Dunlap [this message]
2011-09-06 18:18 ` Josh Boyer
2011-09-06 18:30 ` Arnaud Lacombe
2011-09-07 14:08 ` Mauro Carvalho Chehab
2011-09-11 4:19 ` Stephen Rothwell
2011-09-22 1:54 ` Mauro Carvalho Chehab
2011-09-22 2:23 ` Stephen Rothwell
2011-09-22 2:48 ` Mauro Carvalho Chehab
2011-09-22 14:26 ` Stephen Rothwell
2011-09-22 17:48 ` Mauro Carvalho Chehab
2011-09-07 7:16 ` Stephen Rothwell
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=20110906103718.2c57eb3e.rdunlap@xenotime.net \
--to=rdunlap@xenotime$(echo .)net \
--cc=jwboyer@gmail$(echo .)com \
--cc=lacombar@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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