From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] PING-2: [PATCH v4 0/7] qom: more efficient object property handling
Date: Thu, 5 Nov 2015 17:51:31 +0100 [thread overview]
Message-ID: <563B8913.7030207@suse.de> (raw)
In-Reply-To: <013301d110aa$4df435f0$e9dca1d0$@samsung.com>
Pavel,
Am 27.10.2015 um 12:26 schrieb Pavel Fedin:
>>> I can further test cases to do more coverage of object proprty handling
>>> wrt to classes, if you want me to.
>>
>> No, if that is sorted out now, I'll drop v2 and need to review v4.
>
> How is it? Any problems / advancements? Could i help somehow?
It would help more if your "PING" messages actually brought up the
relevant thread. However they arrive as single messages here...
(no References header)
Regards,
Andreas
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)
prev parent reply other threads:[~2015-11-05 16:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 11:26 [Qemu-devel] PING-2: [PATCH v4 0/7] qom: more efficient object property handling Pavel Fedin
2015-11-05 16:51 ` Andreas Färber [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=563B8913.7030207@suse.de \
--to=afaerber@suse.de \
--cc=qemu-devel@nongnu.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).