From: Greg KH <gregkh@linuxfoundation.org>
To: Kevin Hilman <khilman@baylibre.com>
Cc: Willy Tarreau <w@1wt.eu>, Guenter Roeck <linux@roeck-us.net>,
Fengguang Wu <fengguang.wu@intel.com>,
stable@vger.kernel.org, lkml <linux-kernel@vger.kernel.org>,
Milo Casagrande <milo.casagrande@linaro.org>,
Tyler Baker <tyler.baker@linaro.org>
Subject: Re: Stable -rc git trees and email headers
Date: Wed, 22 Jun 2016 15:42:50 -0700 [thread overview]
Message-ID: <20160622224250.GA20774@kroah.com> (raw)
In-Reply-To: <CAOi56cU4vVSRmNRX4cCwqqcDdOzAQC_qyN3AFg8jG3hU=LNmRw@mail.gmail.com>
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
prev parent reply other threads:[~2016-06-22 22:42 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
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 [this message]
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=20160622224250.GA20774@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=milo.casagrande@linaro.org \
--cc=stable@vger.kernel.org \
--cc=tyler.baker@linaro.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).