From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Thomas Huth" <thuth@redhat.com>,
sheepdog@lists.wpkg.org, qemu-block@nongnu.org,
libvir-list@redhat.com, "Markus Armbruster" <armbru@redhat.com>,
"Max Reitz" <mreitz@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Liu Yuan" <namei.unix@gmail.com>
Subject: [PATCH v2 0/2] block: deprecate the sheepdog driver
Date: Tue, 22 Sep 2020 17:16:09 +0100 [thread overview]
Message-ID: <20200922161611.2049616-1-berrange@redhat.com> (raw)
2 years back I proposed dropping the sheepdog mailing list from the
MAINTAINERS file, but somehow the patch never got picked up:
https://lists.gnu.org/archive/html/qemu-block/2018-03/msg01048.html
So here I am with the same patch again.
This time I go further and deprecate the sheepdog driver entirely.
See the rationale in the second patch commit message.
Daniel P. Berrangé (2):
block: drop moderated sheepdog mailing list from MAINTAINERS file
block: deprecate the sheepdog block driver
MAINTAINERS | 1 -
block/sheepdog.c | 15 +++++++++++++++
configure | 5 +++--
docs/system/deprecated.rst | 9 +++++++++
4 files changed, 27 insertions(+), 3 deletions(-)
--
2.26.2
next reply other threads:[~2020-09-22 16:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 16:16 Daniel P. Berrangé [this message]
2020-09-22 16:16 ` [PATCH v2 1/2] block: drop moderated sheepdog mailing list from MAINTAINERS file Daniel P. Berrangé
2020-09-22 17:27 ` Thomas Huth
2020-09-22 17:46 ` Vladimir Sementsov-Ogievskiy
2020-09-22 16:16 ` [PATCH v2 2/2] block: deprecate the sheepdog block driver Daniel P. Berrangé
2020-09-22 17:32 ` Thomas Huth
2020-09-22 17:53 ` Vladimir Sementsov-Ogievskiy
2020-09-23 10:25 ` Philippe Mathieu-Daudé
2020-09-23 13:50 ` Markus Armbruster
2020-09-22 17:09 ` [PATCH v2 0/2] block: deprecate the sheepdog driver Neal Gompa
2020-09-22 17:42 ` Daniel P. Berrangé
2020-09-22 18:11 ` Neal Gompa
2020-09-23 4:52 ` Vladimir Sementsov-Ogievskiy
2020-09-23 8:24 ` Peter Krempa
2020-09-22 21:10 ` no-reply
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=20200922161611.2049616-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=kwolf@redhat.com \
--cc=libvir-list@redhat.com \
--cc=mreitz@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.