From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
Sasha Levin <sasha.levin@oracle.com>
Subject: Re: [PATCH kernel.org] 4.1 is now maintained by Sasha Levin
Date: Mon, 1 Feb 2016 09:57:03 -0500 [thread overview]
Message-ID: <20160201145703.GA22073@gmail.com> (raw)
In-Reply-To: <20160131194152.GA25157@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 462 bytes --]
On Sun, Jan 31, 2016 at 11:41:52AM -0800, Greg KH wrote:
> Sasha has volunteered to maintain the 4.1-longterm kernel for some
> strange and insane reason. So quick, before he comes to his senses,
> mark 4.1 as being maintained by him publicly so that the world will
> know.
Sasha's insanity is now publicly documented on
https://kernel.org/releases.html
Best regards,
--
Konstantin Ryabitsev
Linux Foundation Collab Projects
Montréal, Québec
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-02-01 14:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-31 19:41 [PATCH kernel.org] 4.1 is now maintained by Sasha Levin Greg KH
2016-02-01 14:57 ` Konstantin Ryabitsev [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=20160201145703.GA22073@gmail.com \
--to=konstantin@linuxfoundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
--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 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).