From mboxrd@z Thu Jan  1 00:00:00 1970
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Subject: Re: linux-next: Tree for Nov 2
Date: Fri, 2 Nov 2018 11:44:07 +0100
Message-ID: <CANiq72m65bQZefAoFF5dTUB-rPzm4vofZFnDn0nYBG3MsGrjZg@mail.gmail.com>
References: <20181102143018.09feb051@canb.auug.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <20181102143018.09feb051@canb.auug.org.au>
Sender: linux-kernel-owner@vger.kernel.org
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-Next Mailing List <linux-next@vger.kernel.org>, linux-kernel <linux-kernel@vger.kernel.org>
List-Id: linux-next.vger.kernel.org

Hi Stephen,

On Fri, Nov 2, 2018 at 4:33 AM Stephen Rothwell <sfr@canb.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