From: Markus Armbruster <armbru@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Liu Yuan" <namei.unix@gmail.com>,
sheepdog@lists.wpkg.org,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH 0/1] block: future of sheepdog storage driver ?
Date: Tue, 22 Sep 2020 15:25:23 +0200 [thread overview]
Message-ID: <87d02eose4.fsf@dusky.pond.sub.org> (raw)
In-Reply-To: <0073f0f8-2a59-9bad-3088-4790ec07fe31@redhat.com> (Thomas Huth's message of "Tue, 22 Sep 2020 12:32:37 +0200")
Thomas Huth <thuth@redhat.com> writes:
> On 22/09/2020 11.01, Daniel P. Berrangé wrote:
> [...]
>> Does someone have a compelling reason for QEMU to keep supporting
>> this driver, other than the fact that it already exists ?
>>
>> If not, it looks like a candidate for deprecating in QEMU with a
>> view to later removing it.
>
> I think you gave enough examples why this is a good candidate for
> deprecation. So I'd say: Simply send a patch to deprecate it. That's
> what's our deprecation process is good for. If someone still cares for
> sheepdog, they then can speak up and we can revert the patch that put it
> on the deprecation list.
Concur.
prev parent reply other threads:[~2020-09-22 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 9:01 [PATCH 0/1] block: future of sheepdog storage driver ? Daniel P. Berrangé
2020-09-22 9:01 ` [PATCH 1/1] block: drop moderated sheepdog mailing list from MAINTAINERS file Daniel P. Berrangé
2020-09-22 13:19 ` Philippe Mathieu-Daudé
2020-09-22 10:32 ` [PATCH 0/1] block: future of sheepdog storage driver ? Thomas Huth
2020-09-22 13:25 ` Markus Armbruster [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=87d02eose4.fsf@dusky.pond.sub.org \
--to=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=namei.unix@gmail.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sheepdog@lists.wpkg.org \
--cc=thuth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.