From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Thomas Huth" <thuth@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>,
QEMU <qemu-devel@nongnu.org>,
ashmit602@gmail.com
Cc: Kevin Wolf <kwolf@redhat.com>, Jeff Cody <codyprime@gmail.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: Is VXHS actually maintained?
Date: Thu, 9 Jul 2020 17:25:13 +0200 [thread overview]
Message-ID: <9a7b3b05-b667-d442-e9a3-27daf90a339c@redhat.com> (raw)
In-Reply-To: <2666aec2-9872-6af6-7705-d7ce553f611c@redhat.com>
On 7/9/20 5:20 PM, Thomas Huth wrote:
> On 09/07/2020 17.10, Marc-André Lureau wrote:
>> Hi,
>>
>> VXHS block device was added ~3y ago in commit da92c3ff60b (block/vxhs.c:
>> Add support for a new block device type called "vxhs"), but it doesn't
>> compile anymore, at least since v5.0 (I haven't checked earlier).
>>
>> The upstream repository (https://github.com/VeritasHyperScale/libqnio)
>> hasn't received any update since then.
>>
>> What should we do about it?
>
> IMHO: Mark it as deprecated in docs/system/deprecated.rst, then remove
> it in two releases if nobody shows up to maintain it.
Considering "it doesn't compile anymore", 2 releases is generous :)
next prev parent reply other threads:[~2020-07-09 15:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 15:10 Is VXHS actually maintained? Marc-André Lureau
2020-07-09 15:20 ` Thomas Huth
2020-07-09 15:25 ` Philippe Mathieu-Daudé [this message]
2020-07-09 15:26 ` Daniel P. Berrangé
2020-07-09 15:30 ` Peter Maydell
2020-07-09 15:41 ` Marc-André Lureau
2020-07-09 15:47 ` Peter Maydell
2020-07-09 15:50 ` Alex Bennée
2020-07-09 15:51 ` Peter Maydell
2020-07-09 16:02 ` Marc-André Lureau
2020-07-09 16:25 ` Alex Bennée
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=9a7b3b05-b667-d442-e9a3-27daf90a339c@redhat.com \
--to=philmd@redhat.com \
--cc=ashmit602@gmail.com \
--cc=codyprime@gmail.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=mreitz@redhat.com \
--cc=qemu-devel@nongnu.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 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).