From: Andrew Morton <akpm@linux-foundation.org>
To: Greg <gvrose8192@gmail.com>
Cc: Vladimir Davydov <vdavydov.dev@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Update my e-mail address
Date: Wed, 31 Aug 2016 11:29:56 -0700 [thread overview]
Message-ID: <20160831112956.eb03d75a4b382d4e8cdf0054@linux-foundation.org> (raw)
In-Reply-To: <1472653603.3889.0.camel@gmail.com>
On Wed, 31 Aug 2016 07:26:43 -0700 Greg <gvrose8192@gmail.com> wrote:
> On Wed, 2016-08-31 at 15:01 +0300, Vladimir Davydov wrote:
> > vdavydov@{parallels,virtuozzo}.com will bounce from now on.
> >
> > Signed-off-by: Vladimir Davydov <vdavydov.dev@gmail.com>
>
> Shouldn't MAINTAINERS be in the subject line?
Welcome to my life ;)
This will go in as "MAINTAINERS: Vladimir has moved".
prev parent reply other threads:[~2016-08-31 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 12:01 [PATCH] Update my e-mail address Vladimir Davydov
2016-08-31 14:26 ` Greg
2016-08-31 18:07 ` Vladimir Davydov
2016-08-31 18:29 ` Andrew Morton [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=20160831112956.eb03d75a4b382d4e8cdf0054@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=gvrose8192@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vdavydov.dev@gmail.com \
/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).