From: Eric Blake <eblake@redhat.com>
To: Vladimir Sementsov-Ogievskiy <v.sementsov-og@mail.ru>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH v2] MAINTAINERS: change Vladimir's email address
Date: Mon, 21 Mar 2022 15:12:51 -0500 [thread overview]
Message-ID: <20220321201251.ohhzthftzmijihf2@redhat.com> (raw)
In-Reply-To: <3e0a174c-71e1-2308-855e-0cc9102a8ee0@mail.ru>
On Thu, Mar 17, 2022 at 11:24:28AM +0300, Vladimir Sementsov-Ogievskiy wrote:
> 17.03.2022 00:36, Eric Blake wrote:
> > On Wed, Mar 16, 2022 at 12:27:02PM +0300, Vladimir Sementsov-Ogievskiy wrote:
> > > Old vsementsov@virtuozzo.com is not accessible anymore.
> > >
> > > Signed-off-by: Vladimir Sementsov-Ogievskiy <v.sementsov-og@mail.ru>
> > > ---
> > >
> > > v2: @ya.ru mailbox works bad with mailing lists and git send-email
> > > command, @mail.ru works normally.
> > >
> > > Probably, I'll have to change the email again in the near future. May be
> > > not. But I think it worth to change it now to something that works.
> >
> > Same comment as with your attempt with @ya.ru - I'm happy to
> > incorporate this through my NBD tree, but want to confirm that we had
> > a round-trip conversation so that you are happy with the address
> > working to your needs.
> >
>
> It works)
Okay, I'm queueing this up through my NBD tree. Do you also want to
tweak .mailmap and/or contrib/gitdm/aliases?
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2022-03-21 20:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-16 9:27 [PATCH v2] MAINTAINERS: change Vladimir's email address Vladimir Sementsov-Ogievskiy
2022-03-16 21:36 ` Eric Blake
2022-03-17 8:24 ` Vladimir Sementsov-Ogievskiy
2022-03-21 20:12 ` Eric Blake [this message]
2022-03-21 20:31 ` Vladimir Sementsov-Ogievskiy
2022-03-21 20:44 ` Eric Blake
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=20220321201251.ohhzthftzmijihf2@redhat.com \
--to=eblake@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=v.sementsov-og@mail.ru \
/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).