[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4d515a65c6ce9ef182cab4f2dff08979d58cf7e6.camel@HansenPartnership.com>
Date: Fri, 25 Jun 2021 14:52:13 -0700
From: James Bottomley <James.Bottomley@...senPartnership.com>
To: Benjamin LaHaise <ben@...munityfibre.ca>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: linux-mm@...ck.org - limping on a backup
On Fri, 2021-06-25 at 15:26 -0400, Benjamin LaHaise wrote:
> On Fri, Jun 25, 2021 at 12:21:24PM -0700, James Bottomley wrote:
> > On Fri, 2021-06-25 at 13:12 -0400, Benjamin LaHaise wrote:
> > > On Fri, Jun 25, 2021 at 10:00:15AM -0700, James Bottomley wrote:
> > > > Perhaps it's time to move this list over to vger or the
> > > > linux.dev infrastructure now that it's being brought up? We
> > > > already migrated the containers list without too much pain.
> > >
> > > Maybe the btrfs bugs should get fixed.
> >
> > I believe we can do both.
>
> If I were unresponsive at fixing issues, I would understand the need
> to migrate services, but steps to address the failures have already
> been taken and additional mitigations are planned. If we migrated
> services every time a piece of hardware failed or we hit a kernel
> bug, then we wouldn't have any infrastructure left.
It's not about response time, it's about the fact that we finally got
kerne.org funded via the LF to pay for someone to run our mailing list
infrastructure so we no longer have to do it ourselves. We've already
transferred the containers mailman list and vger is going to be
migrated to it soon. The new infrastructure comes with HA and a whole
host of backend CDN data centres in various geographies and public
inbox backing, so it should be quite slick.
James
Powered by blists - more mailing lists