Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1425619 > unrolled thread

Stable -rc git trees and email headers

Back to article view | Back to linux.kernel

Contents

  Stable -rc git trees and email headers Greg KH <gregkh@linuxfoundation.org> - 2016-06-18 05:20 +0200
    Re: Stable -rc git trees and email headers Guenter Roeck <linux@roeck-us.net> - 2016-06-18 06:20 +0200
    Re: Stable -rc git trees and email headers Fengguang Wu <fengguang.wu@intel.com> - 2016-06-18 07:30 +0200
      Re: Stable -rc git trees and email headers Greg KH <gregkh@linuxfoundation.org> - 2016-06-18 18:40 +0200
      Re: Stable -rc git trees and email headers Jiri Slaby <jslaby@suse.cz> - 2016-06-20 10:50 +0200
        Re: Stable -rc git trees and email headers Fengguang Wu <fengguang.wu@intel.com> - 2016-06-20 11:50 +0200
          Re: Stable -rc git trees and email headers Jiri Slaby <jslaby@suse.cz> - 2016-06-20 12:00 +0200
            Re: Stable -rc git trees and email headers Fengguang Wu <fengguang.wu@intel.com> - 2016-06-20 12:30 +0200
    Re: Stable -rc git trees and email headers Willy Tarreau <w@1wt.eu> - 2016-06-18 07:40 +0200
      Re: Stable -rc git trees and email headers Guenter Roeck <linux@roeck-us.net> - 2016-06-18 17:20 +0200
        Re: Stable -rc git trees and email headers Greg KH <gregkh@linuxfoundation.org> - 2016-06-18 18:40 +0200
          Re: Stable -rc git trees and email headers Guenter Roeck <linux@roeck-us.net> - 2016-06-18 19:00 +0200
    Re: Stable -rc git trees and email headers Kevin Hilman <khilman@baylibre.com> - 2016-06-20 20:20 +0200
    Re: Stable -rc git trees and email headers Kevin Hilman <khilman@baylibre.com> - 2016-06-22 17:10 +0200
      Re: Stable -rc git trees and email headers Greg KH <gregkh@linuxfoundation.org> - 2016-06-22 17:20 +0200
        Re: Stable -rc git trees and email headers Willy Tarreau <w@1wt.eu> - 2016-06-22 17:20 +0200
          Re: Stable -rc git trees and email headers Kevin Hilman <khilman@baylibre.com> - 2016-06-22 19:20 +0200
            Re: Stable -rc git trees and email headers Greg KH <gregkh@linuxfoundation.org> - 2016-06-23 00:50 +0200

#1425619 — Stable -rc git trees and email headers

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?

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,

thanks,

greg k-h

[toc] | [next] | [standalone]

#1425639

Hi Greg,

On 06/17/2016 08:16 PM, 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
>
Great!

> 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?
>
Yes, it does. I'll see if I can switch to fetching the branches from there
in the next couple of days. I'm all happy ...

Thanks!

Guenter

[toc] | [prev] | [next] | [standalone]

#1425646

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.

> And can I get announcements if/when the tests pass (or fail) so I know
> all is ok?

OK.

Thanks,
Fengguang

[toc] | [prev] | [next] | [standalone]

#1425790

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

[toc] | [prev] | [next] | [standalone]

#1426339

On 06/18/2016, 07:22 AM, 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!

Hi,

may I ask to add the 3.12 stable tree to the testing pipeline too?

git://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux-stable.git

thanks,
-- 
js
suse labs

[toc] | [prev] | [next] | [standalone]

#1426436

Hi Jiri,

On Mon, Jun 20, 2016 at 10:39:37AM +0200, Jiri Slaby wrote:
> On 06/18/2016, 07:22 AM, 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!
> 
> Hi,
> 
> may I ask to add the 3.12 stable tree to the testing pipeline too?
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/jirislaby/linux-stable.git

It looks already in the testing pipeline. :)

https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/tree/repo/linux/jirislaby-stable

Thanks,
Fengguang

[toc] | [prev] | [next] | [standalone]

#1426449

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...

thanks,
-- 
js
suse labs

[toc] | [prev] | [next] | [standalone]

#1426469

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

[toc] | [prev] | [next] | [standalone]

#1425649

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.

Cheers,
Willy

[toc] | [prev] | [next] | [standalone]

#1425742

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

[toc] | [prev] | [next] | [standalone]

#1425791

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

[toc] | [prev] | [next] | [standalone]

#1425797

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@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?
>

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

Guenter

[toc] | [prev] | [next] | [standalone]

#1426906

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

[toc] | [prev] | [next] | [standalone]

#1428877

Hi Greg,

On Fri, Jun 17, 2016 at 8:16 PM, Greg KH <gregkh@linuxfoundation.org> wrote:

[...]

> 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?

Can you add one more:  X-KernelTest-PatchCount ?

Which would include the total number of patches in the series/branch?
This will help us determine uniqueness for a given branch.

Thanks,

Kevin

[toc] | [prev] | [next] | [standalone]

#1428888

On Wed, Jun 22, 2016 at 08:02:14AM -0700, Kevin Hilman wrote:
> Hi Greg,
> 
> On Fri, Jun 17, 2016 at 8:16 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> 
> [...]
> 
> > 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?
> 
> Can you add one more:  X-KernelTest-PatchCount ?
> 
> Which would include the total number of patches in the series/branch?
> This will help us determine uniqueness for a given branch.

What do you mean by "uniqueness"?

As these are going to be the -rc releases, they will be unique from any
other -rc release.

confused,

greg k-h

[toc] | [prev] | [next] | [standalone]

#1428890

On Wed, Jun 22, 2016 at 08:11:41AM -0700, Greg KH wrote:
> On Wed, Jun 22, 2016 at 08:02:14AM -0700, Kevin Hilman wrote:
> > Hi Greg,
> > 
> > On Fri, Jun 17, 2016 at 8:16 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > 
> > [...]
> > 
> > > 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?
> > 
> > Can you add one more:  X-KernelTest-PatchCount ?
> > 
> > Which would include the total number of patches in the series/branch?
> > This will help us determine uniqueness for a given branch.
> 
> What do you mean by "uniqueness"?
> 
> As these are going to be the -rc releases, they will be unique from any
> other -rc release.

I guess he means between incremental updates, though that doesn't work
if you drop a patch.

Willy

[toc] | [prev] | [next] | [standalone]

#1429015

On Wed, Jun 22, 2016 at 8:14 AM, Willy Tarreau <w@1wt.eu> wrote:
> On Wed, Jun 22, 2016 at 08:11:41AM -0700, Greg KH wrote:
>> On Wed, Jun 22, 2016 at 08:02:14AM -0700, Kevin Hilman wrote:
>> > Hi Greg,
>> >
>> > On Fri, Jun 17, 2016 at 8:16 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
>> >
>> > [...]
>> >
>> > > 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?
>> >
>> > Can you add one more:  X-KernelTest-PatchCount ?
>> >
>> > Which would include the total number of patches in the series/branch?
>> > This will help us determine uniqueness for a given branch.
>>
>> What do you mean by "uniqueness"?
>>
>> As these are going to be the -rc releases, they will be unique from any
>> other -rc release.
>
> I guess he means between incremental updates, though that doesn't work
> if you drop a patch.

Right, you add/drop patches as various regressions come in, so the
branch is going to keep changing, even though it's going to continue
to be called -rc1.

Actually, now that you're using git trees, even better than patch
count would be just to publish the result of 'git describe' on the
branch you've pushed.  That includes the patch count and the has of
the top commit.

X-KernelTest-GitDescribe?

Kevin

[toc] | [prev] | [next] | [standalone]

#1429179

On Wed, Jun 22, 2016 at 10:12:14AM -0700, Kevin Hilman wrote:
> On Wed, Jun 22, 2016 at 8:14 AM, Willy Tarreau <w@1wt.eu> wrote:
> > On Wed, Jun 22, 2016 at 08:11:41AM -0700, Greg KH wrote:
> >> On Wed, Jun 22, 2016 at 08:02:14AM -0700, Kevin Hilman wrote:
> >> > Hi Greg,
> >> >
> >> > On Fri, Jun 17, 2016 at 8:16 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> >> >
> >> > [...]
> >> >
> >> > > 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?
> >> >
> >> > Can you add one more:  X-KernelTest-PatchCount ?
> >> >
> >> > Which would include the total number of patches in the series/branch?
> >> > This will help us determine uniqueness for a given branch.
> >>
> >> What do you mean by "uniqueness"?
> >>
> >> As these are going to be the -rc releases, they will be unique from any
> >> other -rc release.
> >
> > I guess he means between incremental updates, though that doesn't work
> > if you drop a patch.
> 
> Right, you add/drop patches as various regressions come in, so the
> branch is going to keep changing, even though it's going to continue
> to be called -rc1.
> 
> Actually, now that you're using git trees, even better than patch
> count would be just to publish the result of 'git describe' on the
> branch you've pushed.  That includes the patch count and the has of
> the top commit.
> 
> X-KernelTest-GitDescribe?

Ugh, my emails and git tree creations are separate scripts.  Well,
kinda, it's all a big mess.  I'll try add this later on, let's start
with the ones we have now and see if those help out :)

thanks,

greg k-h

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web