From: Max Reitz <mreitz@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] [PULL for-2.9] block: Declare blockdev-add and blockdev-del supported
Date: Tue, 28 Mar 2017 21:54:30 +0200 [thread overview]
Message-ID: <b1fa7bd5-0b78-b15a-46ce-6efc871e583f@redhat.com> (raw)
In-Reply-To: <87zig5s0ck.fsf@dusky.pond.sub.org>
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
On 28.03.2017 20:49, Markus Armbruster wrote:
> Paolo Bonzini <pbonzini@redhat.com> writes:
>
>> On 28/03/2017 15:45, Markus Armbruster wrote:
>>> It's been a long journey, but here we are.
>>>
>>> The supported blockdev-add is not compatible to its experimental
>>> predecessors; bump all Since: tags to 2.9.
>>
>> Can you document the differences in the 2.9 changelog?
>
> Not sure I can before I drop off for a week of vacation. Kevin, Max,
> can you chip in?
Just document the changes we have done to blockdev-add since it was
originally introduced? Sure, I'll have a shot.
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
next prev parent reply other threads:[~2017-03-28 19:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-28 13:45 [Qemu-devel] [PULL for-2.9] Block patches for 2017-03-28 Markus Armbruster
2017-03-28 13:45 ` [Qemu-devel] [PULL for-2.9] block: Declare blockdev-add and blockdev-del supported Markus Armbruster
2017-03-28 14:18 ` Paolo Bonzini
2017-03-28 18:49 ` Markus Armbruster
2017-03-28 19:54 ` Max Reitz [this message]
2017-03-28 14:56 ` [Qemu-devel] [PULL for-2.9] Block patches for 2017-03-28 Peter Maydell
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=b1fa7bd5-0b78-b15a-46ce-6efc871e583f@redhat.com \
--to=mreitz@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--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).