From: Jiri Slaby <jslaby@suse.cz>
To: Greg KH <gregkh@linuxfoundation.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH] 4.4 will be the next longterm kernel
Date: Mon, 2 Nov 2015 15:29:51 +0100 [thread overview]
Message-ID: <5637735F.4090608@suse.cz> (raw)
In-Reply-To: <20151028204105.GA13060@kroah.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 10/28/2015, 09:41 PM, Greg KH wrote:
> From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>
> As a result of the discussion at the 2015 Linux Kernel summit, the
> 4.4 kernel will be the next longterm kernel release
Hi Greg,
since we will base our product on 4.4, whenever you feel you could
spend your time better on something else, I can continue taking care
of 4.4.x afterwards.
thanks,
- --
js
suse labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJWN3NcAAoJEL0lsQQGtHBJ4bEQAK475o3AVTpMrPv7GLxOqEi+
Yzh3RI0VUB4Nuu96FxhOeg8WbqPLgetvPQ7ud2vDIiRXD/k209ATkXfIBPBV2kNF
PAb5cZaA+YHWizE8FnwNgPm6PBYSdBfb7bBcdl7zi1MexX2kEAibSBgVS9h7WUNo
fjcSGOOYhFqwM9W2f6vLOXRqIqoYbPd/YAL6n0P72ZoIFcsHGFVIAxu6UL+TE1Jw
csQVj0No91YvvYi2YQ7fs/Zq7GPep6CqgodO137x2s7F8qu5J04TyIDnda2JYio3
dqJlexR439tKBo3NcbPokfE+14QFIFPBRNpxU+iEoQ3Z+Pcvh+qBLJ4D3BBJGFWM
CfURPbZOaq8pYVzY3NOu4yMXUC7d6miduOHzQ71HwItRpIBLdYlvPERiGKXl8GLY
E1t6+cdh5Qho12RnYDQ0Va+Fx1mhRuEuBJ+Wc1SCAZ/C0QU1Bpfj/pL7kME5a/sM
AfmD+rdshma1hPzW9lV+s6M1lbziwRb6Cg7TINsVX/j299kyQlgYkTjgRHoCqZca
ZdcQbc06KniGAm/o2+3ehUxa6hXUC/VkALoTe5rprTaMfSPL9gTNRuFkaECkpU7Z
EM/YuvHY+SybAlejqDXKJZ39oYwvgxNqeCSWpxw8fkzAQXzpJfe6oEli2exj74Bg
jZbTFD6/TXIv3UfrYxBO
=NLI/
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-11-02 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 20:41 [PATCH] 4.4 will be the next longterm kernel Greg KH
2015-11-02 14:29 ` Jiri Slaby [this message]
2015-11-02 14:34 ` Willy Tarreau
2015-11-09 18:24 ` Konstantin Ryabitsev
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=5637735F.4090608@suse.cz \
--to=jslaby@suse.cz \
--cc=gregkh@linuxfoundation.org \
--cc=konstantin@linuxfoundation.org \
--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.