From: Greg KH <gregkh@linuxfoundation.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Kevin Hilman <khilman@baylibre.com>,
Guenter Roeck <linux@roeck-us.net>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Stable -rc git trees and email headers
Date: Sat, 18 Jun 2016 09:35:49 -0700 [thread overview]
Message-ID: <20160618163549.GB32242@kroah.com> (raw)
In-Reply-To: <20160618052232.GA19292@wfg-t540p.sh.intel.com>
On Sat, Jun 18, 2016 at 01:22:32PM +0800, Fengguang Wu wrote:
> Hi Greg,
>
> On Fri, Jun 17, 2016 at 08:16:20PM -0700, Greg KH wrote:
> > Hi,
> >
> > I've finally gotten off my butt and made my quilt trees of patches into
> > a "semi-proper" git tree to make it easier for people to test them.
> >
> > I'm now pushing the patches I accept into the stable queues into the git
> > tree here:
> > git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
>
> > Fengguang, can you add these to the 0-day bot?
>
> Sure. It's great to see these early testing branches!
>
> > The branches to watch are all of the currently-active stable trees.
> > Right now that would be "linux-3.14.y", "linux-4.4.y", and
> > "linux-4.6.y". Do I need to tell you about future branches, or can
> > you just pick up new ones when they show up?
>
> The robot will auto pick new branches up.
Wonderful, thanks for adding it.
greg k-h
next prev parent reply other threads:[~2016-06-18 16:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 3:16 Stable -rc git trees and email headers Greg KH
2016-06-18 4:15 ` Guenter Roeck
2016-06-18 5:22 ` Fengguang Wu
2016-06-18 16:35 ` Greg KH [this message]
2016-06-20 8:39 ` Jiri Slaby
2016-06-20 9:39 ` Fengguang Wu
2016-06-20 9:52 ` Jiri Slaby
2016-06-20 10:22 ` Fengguang Wu
2016-06-18 5:29 ` Willy Tarreau
2016-06-18 15:12 ` Guenter Roeck
2016-06-18 16:35 ` Greg KH
2016-06-18 16:53 ` Guenter Roeck
2016-06-20 18:09 ` Kevin Hilman
2016-06-22 15:02 ` Kevin Hilman
2016-06-22 15:11 ` Greg KH
2016-06-22 15:14 ` Willy Tarreau
2016-06-22 17:12 ` Kevin Hilman
2016-06-22 22:42 ` Greg KH
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=20160618163549.GB32242@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=fengguang.wu@intel.com \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=stable@vger.kernel.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