From: Greg KH <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Willy Tarreau <w@1wt.eu>, Kevin Hilman <khilman@baylibre.com>,
Fengguang Wu <fengguang.wu@intel.com>,
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:36 -0700 [thread overview]
Message-ID: <20160618163536.GA32242@kroah.com> (raw)
In-Reply-To: <576564E2.5000705@roeck-us.net>
On Sat, Jun 18, 2016 at 08:12:34AM -0700, Guenter Roeck wrote:
> On 06/17/2016 10:29 PM, Willy Tarreau 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
> > >
> > > 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.
> >
> > Do you mean you'll tag them when you issue a review ? If so, maybe that
> > can help our testers automatically trigger a series of tests when they
> > spot a tag that was not tested yet instead of having to monitor emails ?
> > If that's the case, I have no issue with pushing a tag when I emit a
> > series as well.
> >
>
> I think he means that the topmost patch is similar to the following
> (taken from 4.6.y).
>
> Guenter
>
> ---
> commit f1976bc9e10f2abcea081a9d8bcf05e8633ea6ab
> Author: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Date: Fri Jun 17 19:50:50 2016 -0700
>
> Linux 4.6.3-rc1
>
> diff --git a/Makefile b/Makefile
> index 93068c2..47737f2 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -1,7 +1,7 @@
> VERSION = 4
> PATCHLEVEL = 6
> -SUBLEVEL = 2
> -EXTRAVERSION =
> +SUBLEVEL = 3
> +EXTRAVERSION = -rc1
> NAME = Charred Weasel
Yeah, right now my scripts add that. Is it worth me not having that
there until I do an -rc release? Or is it ok as-is?
thanks,
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
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 [this message]
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=20160618163536.GA32242@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 \
--cc=w@1wt.eu \
/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).