[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72m65bQZefAoFF5dTUB-rPzm4vofZFnDn0nYBG3MsGrjZg@mail.gmail.com>
Date: Fri, 2 Nov 2018 11:44:07 +0100
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: Tree for Nov 2
Hi Stephen,
On Fri, Nov 2, 2018 at 4:33 AM Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> Hi all,
>
> Please do not add any v4.21/v5.1 code to your linux-next included trees
> until after the merge window closes.
Is it OK to move forward the branch up to the point where it landed in
mainline, no? What about changes for this release that will be sent
for -rc2, -rc3... etc.?
Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists