From: Kalle Valo <kvalo@codeaurora.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>,
Sasha Levin <Alexander.Levin@microsoft.com>,
Linus <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: linux-next: a new pending-fixes branch
Date: Sat, 12 May 2018 10:14:19 +0300 [thread overview]
Message-ID: <87603t1h2s.fsf@purkki.adurom.net> (raw)
In-Reply-To: <20180512143523.250ab803@canb.auug.org.au> (Stephen Rothwell's message of "Sat, 12 May 2018 14:35:23 +1000")
Stephen Rothwell <sfr@canb.auug.org.au> writes:
> 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).
>
> It would be good if this branch could be tested by the 0-Day service
> and any other testing that people do - in the hope of sending fewer
> "fixes causing bugs" patches to Linus.
>
> There is not intention that bug fixes for Linus' tree should
> necessarily be tested in linux-next before being forwarded, but
> (especially for slightly less urgent bugs, at least) it seems like a
> good idea.
>
> I currently have 55 branches of bug fixes included.
Is there a list of branches you use available somewhere? I would like to
check that wireless-drivers is included.
--
Kalle Valo
next prev parent reply other threads:[~2018-05-12 7:14 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 [this message]
2018-05-12 7:50 ` Stephen Rothwell
2018-05-17 17:42 ` Sasha Levin
2018-05-17 20:46 ` Stephen Rothwell
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=87603t1h2s.fsf@purkki.adurom.net \
--to=kvalo@codeaurora.org \
--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=sfr@canb.auug.org.au \
--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