[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMuHMdVHXYhXtyMAR84L5kQTSU8Ds71AJftrEBqepiy_NV88kA@mail.gmail.com>
Date: Fri, 6 Dec 2019 11:15:49 +0100
From: Geert Uytterhoeven <geert@...ux-m68k.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Dec 6
Hi Stephen,
On Fri, Dec 6, 2019 at 3:55 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Changes since 20191204:
Hm, yesterday there was a next-20191205.
>
> The printk tree gained a semantic conflict against Linus' tree.
>
> The vhost tree still had its build failures so I used the version from
> next-20191203.
>
> Non-merge commits (relative to Linus' tree): 1311
> 1429 files changed, 36236 insertions(+), 14987 deletions(-)
>
> ----------------------------------------------------------------------------
>
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Thanks!
Looks like the next-20191206 tag didn't make it to kernel.org, but the
master branch was updated (so I'm happy :-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Powered by blists - more mailing lists