From mboxrd@z Thu Jan  1 00:00:00 1970
From: Sasha Levin <Alexander.Levin@microsoft.com>
Subject: Re: linux-next: a new pending-fixes branch
Date: Thu, 17 May 2018 17:42:49 +0000
Message-ID: <20180517174247.GI8514@sasha-vm>
References: <20180512143523.250ab803@canb.auug.org.au>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <20180512143523.250ab803@canb.auug.org.au>
Content-Language: en-US
Content-ID: <B786F4B7A3AB694292676B980981013C@namprd21.prod.outlook.com>
Sender: linux-kernel-owner@vger.kernel.org
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux-kernel Mailing List <linux-kernel@vger.kernel.org>, Linux-Next Mailing List <linux-next@vger.kernel.org>, 0-Day Mailing List <lkp@lists.01.org>, Linus <torvalds@linux-foundation.org>, Andrew Morton <akpm@linux-foundation.org>
List-Id: linux-next.vger.kernel.org

On Sat, May 12, 2018 at 02:35:23PM +1000, Stephen Rothwell wrote:
>Hi all,
>
>As an outcome of some discussion, I have added a pending-fixes branch
>to linux-next.  This branch contains Linus' tree merged with branches
>containing only fixes pending for the current release.  The branch is a
>strict subset of linux-next each day (as so rebases like linux-next
>does).

will you be keeping a history of this branch like the linux-next history
tree?