All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Greg KH <gregkh@linuxfoundation.org>,
	Kevin Hilman <khilman@baylibre.com>,
	Fengguang Wu <fengguang.wu@intel.com>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Stable -rc git trees and email headers
Date: Fri, 17 Jun 2016 21:15:56 -0700	[thread overview]
Message-ID: <5764CAFC.40802@roeck-us.net> (raw)
In-Reply-To: <20160618031620.GA14082@kroah.com>

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

  reply	other threads:[~2016-06-18  4:16 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 [this message]
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

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=5764CAFC.40802@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=fengguang.wu@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=khilman@baylibre.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.