From: "Denis V. Lunev" <den@openvz.org>
To: Laszlo Ersek <lersek@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Dmitry Andreev <dandreev@virtuozzo.com>,
qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/1] blk: do not select PFLASH device for internal snapshot
Date: Wed, 13 Jan 2016 14:11:40 +0300 [thread overview]
Message-ID: <569630EC.5050209@openvz.org> (raw)
In-Reply-To: <569628FB.3020204@redhat.com>
On 01/13/2016 01:37 PM, Laszlo Ersek wrote:
> meta comment here:
>
> On 01/12/16 16:47, Denis V. Lunev wrote:
>
>> P.S. Here is a summary that my colleague has receiver from libvirt
>> list.
>>
>> -------- Forwarded Message --------
>> Subject: Re: Snapshotting OVMF guests
>> Date: Mon, 11 Jan 2016 13:56:29 +0100
>> From: Laszlo Ersek <lersek@redhat.com>
>> To: Dmitry Andreev <dandreev@virtuozzo.com>
>> CC: Michal Privoznik <mprivozn@redhat.com>, Markus Armbruster
>> <armbru@redhat.com>
>>
>> Hello Dmitry,
>>
>> [...]
> Your colleague Dmitry did not receive this from the libvirt list. He
> received the from me in private. See the headers above.
>
> Please do not publicize a private exchange without asking for permission
> first.
>
> In the present case I don't mind it. I stand by everything I said, and I
> would have written mostly the same if I had been contacted publicly,
> on-list.
>
> But if you contact me in private *first*, then I expect the discussion
> to remain private. If you want to forward the email to a public list,
> please ask for permission. Otherwise I might consider it more prudent
> for myself to answer all private queries with just "please ask me this
> on the list instead".
>
> I appreciate that you guys are working on this, but let's handle emails
> sensibly.
>
> Thanks
> Laszlo
>
Sorry :( I have not properly checked the message :(
I am guilty..
Den
next prev parent reply other threads:[~2016-01-13 11:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 6:03 [Qemu-devel] [PATCH 1/1] blk: do not select PFLASH device for internal snapshot Denis V. Lunev
2016-01-12 14:16 ` Kevin Wolf
2016-01-12 14:59 ` Paolo Bonzini
2016-01-12 15:13 ` Denis V. Lunev
2016-01-12 15:16 ` Peter Maydell
2016-01-12 15:26 ` Kevin Wolf
2016-01-12 15:20 ` Kevin Wolf
2016-01-12 15:35 ` Paolo Bonzini
2016-01-12 15:47 ` Denis V. Lunev
2016-01-12 16:35 ` Denis V. Lunev
2016-01-12 16:52 ` Kevin Wolf
2016-01-12 16:58 ` Denis V. Lunev
2016-01-12 17:40 ` Markus Armbruster
2016-01-12 17:50 ` Kevin Wolf
2016-01-12 17:54 ` Denis V. Lunev
2016-01-13 8:09 ` Markus Armbruster
2016-01-13 10:43 ` Laszlo Ersek
2016-01-12 17:53 ` Denis V. Lunev
2016-01-13 10:41 ` Laszlo Ersek
2016-01-13 10:37 ` Laszlo Ersek
2016-01-13 11:11 ` Denis V. Lunev [this message]
2016-01-13 12:15 ` Laszlo Ersek
2016-01-12 15:10 ` Denis V. Lunev
2016-01-12 15:28 ` Kevin Wolf
2016-01-14 11:33 ` [Qemu-devel] [PATCH 1/1] RESUME " Denis V. Lunev
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=569630EC.5050209@openvz.org \
--to=den@openvz.org \
--cc=dandreev@virtuozzo.com \
--cc=kwolf@redhat.com \
--cc=lersek@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--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).