Re: Stable -rc git trees and email headers

[Guenter Roeck]

On 06/18/2016 09:35 AM, Greg KH wrote:
> 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@xxxxxxxxxxxxxxxxxxx>
> > 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?

Ok with me. The builders don't care. I use "git describe" to identify versions.

Guenter