From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Wang, Wenchao" <wenchao.wang@intel.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Announcement of aborting HAXM maintenance
Date: Thu, 19 Jan 2023 10:12:21 +0000 [thread overview]
Message-ID: <Y8kXhd2EcRU2QxVC@redhat.com> (raw)
In-Reply-To: <DM6PR11MB40903663BB06C7A64136DF3587C49@DM6PR11MB4090.namprd11.prod.outlook.com>
On Thu, Jan 19, 2023 at 03:56:04AM +0000, Wang, Wenchao wrote:
> Hi, Philippe,
>
> Intel decided to abort the development of HAXM and the maintenance
> of its QEMU part. Should we submit a patch to mark the Guest CPU
> Cores (HAXM) status as Orphan and remove the maintainers from the
> corresponding list? Meanwhile, should the code enabling HAX in QEMU
> once committed by the community be retained?
If you no longer intend to work on QEMU bits related to HAXM, then
yes, you should send a patch for the MAINTAINERS file to remove you
name and mark it as "Orphan" status.
We would not normally delete code from QEMU, merely because it has
been orphaned. If it is still known to work then we would retain
it indefinitely, unless some compelling reason arises to drop it.
This gives time for any potential users to adjust their plans,
and/or opportunity for other interested people to take over the
maintenance role.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2023-01-19 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 3:56 Announcement of aborting HAXM maintenance Wang, Wenchao
2023-01-19 10:12 ` Daniel P. Berrangé [this message]
2023-01-19 10:33 ` Stefan Weil via
2023-01-19 10:37 ` Peter Maydell
2023-01-19 12:40 ` Wang, Wenchao
2023-01-25 15:02 ` Thomas Huth
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=Y8kXhd2EcRU2QxVC@redhat.com \
--to=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wenchao.wang@intel.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.