From: Max Reitz <mreitz@redhat.com>
To: qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, Kevin Wolf <kwolf@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] MAINTAINERS: Add qemu-progress to the block layer
Date: Mon, 8 May 2017 18:28:12 +0200 [thread overview]
Message-ID: <86054675-9a61-f6ad-1d3c-1bef5deae3a6@redhat.com> (raw)
In-Reply-To: <20170428165517.30341-1-mreitz@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 437 bytes --]
On 28.04.2017 18:55, Max Reitz wrote:
> util/qemu-progress.c is currently unmaintained. The only user of its
> functionality is qemu-img, so it effectively is part of the block layer.
>
> Suggested-by: Fam Zheng <famz@redhat.com>
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
Applied to my block branch:
https://github.com/XanClic/qemu/commits/block
Max
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 512 bytes --]
prev parent reply other threads:[~2017-05-08 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 16:55 [Qemu-devel] [PATCH] MAINTAINERS: Add qemu-progress to the block layer Max Reitz
2017-04-28 18:47 ` Eric Blake
2017-05-02 14:10 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-05-08 16:28 ` Max Reitz [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=86054675-9a61-f6ad-1d3c-1bef5deae3a6@redhat.com \
--to=mreitz@redhat.com \
--cc=kwolf@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).