From: Peter Maydell <peter.maydell@linaro.org>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Kevin Wolf" <kwolf@redhat.com>, "Thomas Huth" <thuth@redhat.com>,
"Jeff Cody" <codyprime@gmail.com>, QEMU <qemu-devel@nongnu.org>,
"Max Reitz" <mreitz@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>,
ashmit602@gmail.com
Subject: Re: Is VXHS actually maintained?
Date: Thu, 9 Jul 2020 16:30:40 +0100 [thread overview]
Message-ID: <CAFEAcA_9NUeMJQWuzbmm9raW4zBgu3FFhgCabxBD_RhKMo9GxQ@mail.gmail.com> (raw)
In-Reply-To: <20200709152630.GW3753300@redhat.com>
On Thu, 9 Jul 2020 at 16:27, Daniel P. Berrangé <berrange@redhat.com> wrote:
> If it doesn't even compile, do we even need to go through the full
> deprecation cycle ? I tend to feel like the release where it first
> fails to compile automatically starts the deprecation countdown.
Mmm, assuming that it's "couldn't possibly compile for anybody"
rather than "doesn't compile for me (but maybe it would be OK
on some other host OS config)".
Marc-André, what are the details of the compilation failure?
thanks
-- PMM
next prev parent reply other threads:[~2020-07-09 15:35 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é
2020-07-09 15:26 ` Daniel P. Berrangé
2020-07-09 15:30 ` Peter Maydell [this message]
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=CAFEAcA_9NUeMJQWuzbmm9raW4zBgu3FFhgCabxBD_RhKMo9GxQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=ashmit602@gmail.com \
--cc=berrange@redhat.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).