From: Kevin Hilman <khilman@baylibre.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Fengguang Wu <fengguang.wu@intel.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
milo.casagrande@linaro.org, tyler.baker@linaro.org
Subject: Re: Stable -rc git trees and email headers
Date: Mon, 20 Jun 2016 11:09:48 -0700 [thread overview]
Message-ID: <m2r3brag0j.fsf@baylibre.com> (raw)
In-Reply-To: <20160618031620.GA14082@kroah.com> (Greg KH's message of "Fri, 17 Jun 2016 20:16:20 -0700")
Greg KH <gregkh@linuxfoundation.org> writes:
> 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
>
> I'll push them out in chunks, as I accept them, and when I do a "real"
> -rc release. Right now the HEAD of each branch will have a -rc1 tag on
> them, just because it makes it a bit easier on my end.
>
> Note these branches WILL get rebased. All the time. So don't count on
> them to contain anything that will stick around, UNTIL a real stable
> release happens.
>
> Guenter, I hope this helps with your testing, is there anything that I
> can do here to make it easier for you?
>
> Kevin, hopefully this tree also helps you. I will also be adding some
> email headers to my announcements of the -rc releases that you can
> parse. Here is what they are going to look like for an example release:
>
> X-KernelTest-Patch: http://kernel.org/pub/linux/kernel/v4.x/stable-review/patch-4.4.14-rc1.gz
> X-KernelTest-Tree: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git
> X-KernelTest-Branch: linux-4.4.y
> X-KernelTest-Patches: git://git.kernel.org/pub/scm/linux/kernel/git/stable/stable-queue.git
> X-KernelTest-Version: 4.4.14-rc1
> X-KernelTest-Deadline: 2016-06-20T02:57+00:00
>
> Will those work out?
Yes, those look great. We'll start swtiching the kernelci.org bot over
to this tree and let you know if there's anything else we need.
> Fengguang, can you add these to the 0-day bot? 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?
>
> And can I get announcements if/when the tests pass (or fail) so I know
> all is ok?
>
> Hope this helps people out,
Yes, it does. Thanks!
Kevin
next prev parent reply other threads:[~2016-06-20 18:10 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
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 [this message]
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=m2r3brag0j.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=milo.casagrande@linaro.org \
--cc=stable@vger.kernel.org \
--cc=tyler.baker@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.