From: Fengguang Wu <fengguang.wu@intel.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Greg KH <gregkh@linuxfoundation.org>,
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: Mon, 20 Jun 2016 18:22:11 +0800 [thread overview]
Message-ID: <20160620102211.GA19996@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <5fd8b8c8-29b5-b867-2517-e3c0bde3be8d@suse.cz>
On Mon, Jun 20, 2016 at 11:52:14AM +0200, Jiri Slaby wrote:
> On 06/20/2016, 11:39 AM, Fengguang Wu wrote:
> >> git://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux-stable.git
> >
> > It looks already in the testing pipeline. :)
>
> Oh, and it's there for a quite long already :). But I have never seen an
> e-mail from the robot, I think. I hope it only means that none was sent...
Oops, it should be configured to not skip old kernels:
--- a/repo/linux/jirislaby-stable
+++ b/repo/linux/jirislaby-stable
@@ -1,3 +1,4 @@
url: https://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux-stable.git
owner: Jiri Slaby <jslaby@suse.cz>
notify_build_success_branch: .*
+test_old_branches: .*
That should really enable testing for your stable tree. :)
Thanks,
Fengguang
next prev parent reply other threads:[~2016-06-20 10:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 3:16 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 [this message]
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=20160620102211.GA19996@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--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
all inboxes | Powered by JetHome®