From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Sasha Levin <Alexander.Levin@microsoft.com>
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>
Subject: Re: linux-next: a new pending-fixes branch
Date: Fri, 18 May 2018 06:46:26 +1000 [thread overview]
Message-ID: <20180518064626.3f79e30f@canb.auug.org.au> (raw)
In-Reply-To: <20180517174247.GI8514@sasha-vm>
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
Hi Sasha,
On Thu, 17 May 2018 17:42:49 +0000 Sasha Levin <Alexander.Levin@microsoft.com> wrote:
>
> 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?
I hadn't intended to. Do you think it would be useful/necessary? The
commits themselves will be in the linux-next history tree, just not a
separate branch name.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-05-17 20:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 4:35 linux-next: a new pending-fixes branch Stephen Rothwell
2018-05-12 7:14 ` Kalle Valo
2018-05-12 7:50 ` Stephen Rothwell
2018-05-17 17:42 ` Sasha Levin
2018-05-17 20:46 ` Stephen Rothwell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180518064626.3f79e30f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Alexander.Levin@microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).