qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org,
	John Snow <jsnow@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	mreitz@redhat.com, Stefan Hajnoczi <stefanha@redhat.com>,
	"Denis V. Lunev" <den@openvz.org>
Subject: Re: [PATCH] MAINTAINERS: suggest myself as co-maintainer for Block Jobs
Date: Wed, 3 Feb 2021 11:22:19 +0300	[thread overview]
Message-ID: <e1b4aba3-e94b-de1b-05b4-780f41feb5a8@virtuozzo.com> (raw)
In-Reply-To: <304b3b7c-a58e-901d-7f52-b6efb1c1fbfe@virtuozzo.com>

01.02.2021 19:20, Vladimir Sementsov-Ogievskiy wrote:
> 01.02.2021 17:50, Kevin Wolf wrote:
>> Am 01.02.2021 um 12:03 hat Vladimir Sementsov-Ogievskiy geschrieben:
>>> 28.01.2021 18:28, John Snow wrote:
>>>> On 1/28/21 10:09 AM, Markus Armbruster wrote:
>>>>> Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com> writes:
>>>>>
>>>>>> I'm developing Qemu backup for several years, and finally new backup
>>>>>> architecture, including block-copy generic engine and backup-top filter
>>>>>> landed upstream, great thanks to reviewers and especially to
>>>>>> Max Reitz!
>>>>>>
>>>>>> I also have plans of moving other block-jobs onto block-copy, so that
>>>>>> we finally have one generic block copying path, fast and well-formed.
>>>>>>
>>>>>> So, now I suggest to bring all parts of backup architecture into
>>>>>> "Block Jobs" subsystem (actually, aio_task is shared with qcow2 and
>>>>>> qemu-co-shared-resource can be reused somewhere else, but I'd keep an
>>>>>> eye on them in context of block-jobs) and add myself as co-maintainer.
>>>>>>
>>>>>> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
>>>>>
>>>>> With pleasure:
>>>>> Reviewed-by: Markus Armbruster <armbru@redhat.com>
>>>>>
>>>>
>>>> Absolutely! Glad to see it.
>>>>
>>>> Reviewed-by: John Snow <jsnow@redhat.com>
>>>>
>>>
>>> [..]
>>>
>>>> Great!
>>>>
>>>> Reviewed-by: Max Reitz <mreitz@redhat.com>
>>>
>>> Thanks!
>>>
>>> Could someone pull it?
>>
>> I've put it in my block branch (with s/suggest myself/Add Vladimir/ in
>> the subject line), but I don't know when I'll send the next pull
>> request. If someone else sends one first, feel free to include it with:
>>
>> Acked-by: Kevin Wolf <kwolf@redhat.com>
>>
>>> I don't have any signed PGP key for now, to send pull requests :\
>>> Interesting, could I get one while sitting in Moscow?
>>
>> If you're planning to send pull requests, should a git tree of yours be
>> added to the MAINTAINERS sections, too?
>>
> 
> I didn't add it because of signed key absence. As it turned out, Denis Lunev (my boss) already has a signed key, so it's not a problem.
> 

Unfortunately, Den doesn't have an access to his private key, so this variant doesn't work. So, probably someone could recognize me in a video call?

My key is here: http://keys.gnupg.net/pks/lookup?search=Vladimir+Sementsov-Ogievskiy&fingerprint=on&op=index  (note that there is only one Vladimir Sementsov-Ogievskiy, so I can't imagine who can that be other than me :)

-- 
Best regards,
Vladimir


  parent reply	other threads:[~2021-02-03  8:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28 14:41 [PATCH] MAINTAINERS: suggest myself as co-maintainer for Block Jobs Vladimir Sementsov-Ogievskiy
2021-01-28 15:09 ` Markus Armbruster
2021-01-28 15:28   ` John Snow
2021-02-01 11:03     ` Vladimir Sementsov-Ogievskiy
2021-02-01 13:50       ` Alex Bennée
2021-02-01 14:35         ` Daniel P. Berrangé
2021-02-01 14:50       ` Kevin Wolf
2021-02-01 16:20         ` Vladimir Sementsov-Ogievskiy
2021-02-01 16:58           ` Kevin Wolf
2021-02-01 17:08             ` Vladimir Sementsov-Ogievskiy
2021-02-03  8:22           ` Vladimir Sementsov-Ogievskiy [this message]
2021-02-03 15:57             ` John Snow
2021-01-28 16:22 ` Max Reitz

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=e1b4aba3-e94b-de1b-05b4-780f41feb5a8@virtuozzo.com \
    --to=vsementsov@virtuozzo.com \
    --cc=armbru@redhat.com \
    --cc=den@openvz.org \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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).