[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200826152346.GF988805@cmpxchg.org>
Date: Wed, 26 Aug 2020 11:23:46 -0400
From: Johannes Weiner <hannes@...xchg.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Oscar Salvador <osalvador@...e.de>, broonie@...nel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, linux-next@...r.kernel.org, mhocko@...e.cz,
mm-commits@...r.kernel.org, sfr@...b.auug.org.au
Subject: Re: mmotm 2020-08-24-16-06 uploaded
On Tue, Aug 25, 2020 at 05:30:21PM -0700, Andrew Morton wrote:
> On Tue, 25 Aug 2020 10:45:48 +0200 Oscar Salvador <osalvador@...e.de> wrote:
>
> > On Mon, Aug 24, 2020 at 04:07:25PM -0700, akpm@...ux-foundation.org wrote:
> > > A full copy of the full kernel tree with the linux-next and mmotm patches
> > > already applied is available through git within an hour of the mmotm
> > > release. Individual mmotm releases are tagged. The master branch always
> > > points to the latest release, so it's constantly rebasing.
> > >
> > > https://github.com/hnaz/linux-mm
> >
> > Is it me or this is out of sync?
> >
>
> Seems that way. Maybe Johannes's script needs a new battery?
It looks like github had the hiccups yesterday:
Connection to github.com closed by remote host.
fatal: the remote end hung up unexpectedly
fatal: the remote end hung up unexpectedly
But it's uptodate now.
Powered by blists - more mailing lists