From: Markus Armbruster <armbru@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "Markus Armbruster" <armbru@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
libvir-list@redhat.com,
"Richard Henderson" <richard.henderson@linaro.org>,
qemu-devel@nongnu.org, qemu-arm@nongnu.org,
"Reinoud Zandijk" <reinoud@netbsd.org>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
xen-devel@lists.xenproject.org,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Maxim Levitsky" <mlevitsk@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH 1/2] docs/about: Deprecate 32-bit x86 hosts and qemu-system-i386
Date: Tue, 28 Feb 2023 12:34:19 +0100 [thread overview]
Message-ID: <87h6v6gh1g.fsf@pond.sub.org> (raw)
In-Reply-To: <20230228055016-mutt-send-email-mst@kernel.org> (Michael S. Tsirkin's message of "Tue, 28 Feb 2023 05:51:41 -0500")
"Michael S. Tsirkin" <mst@redhat.com> writes:
> On Tue, Feb 28, 2023 at 11:39:39AM +0100, Markus Armbruster wrote:
>> The question to answer: Is 32 bit x86 worth its upkeep? Two
>> sub-questions: 1. Is it worth the human attention? 2. Is it worth
>> (scarce!) CI minutes?
>
> 3. Is it worth arguing about?
If it's not worth arguing, then we merge Thomas's patch.
next prev parent reply other threads:[~2023-02-28 11:34 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 11:10 [PATCH 0/2] Deprecate support for 32-bit x86 and arm hosts Thomas Huth
2023-02-27 11:10 ` [PATCH 1/2] docs/about: Deprecate 32-bit x86 hosts and qemu-system-i386 Thomas Huth
2023-02-27 11:50 ` Daniel P. Berrangé
2023-02-27 20:12 ` Michael S. Tsirkin
2023-02-27 20:21 ` Richard Henderson
2023-02-28 8:59 ` Michael S. Tsirkin
2023-02-28 12:26 ` Philippe Mathieu-Daudé
2023-02-28 9:00 ` Michael S. Tsirkin
2023-02-28 16:57 ` Richard Henderson
2023-02-27 22:32 ` Philippe Mathieu-Daudé
2023-02-28 7:43 ` Thomas Huth
2023-02-28 7:49 ` Thomas Huth
2023-02-28 8:19 ` Michael S. Tsirkin
2023-02-28 8:59 ` Daniel P. Berrangé
2023-02-28 9:03 ` Michael S. Tsirkin
2023-02-28 9:14 ` Thomas Huth
2023-02-28 9:40 ` Daniel P. Berrangé
2023-02-28 10:11 ` Michael S. Tsirkin
2023-02-28 10:39 ` Markus Armbruster
2023-02-28 10:51 ` Michael S. Tsirkin
2023-02-28 11:12 ` Thomas Huth
2023-02-28 11:24 ` Michael S. Tsirkin
2023-02-28 11:27 ` Daniel P. Berrangé
2023-02-28 11:34 ` Markus Armbruster [this message]
2023-02-28 11:45 ` Michael S. Tsirkin
2023-02-27 20:25 ` Richard Henderson
2023-02-28 7:52 ` Thomas Huth
2023-02-27 11:10 ` [PATCH 2/2] docs/about: Deprecate 32-bit arm hosts and qemu-system-arm Thomas Huth
2023-02-27 18:38 ` [PATCH 0/2] Deprecate support for 32-bit x86 and arm hosts Daniel P. Berrangé
2023-02-28 7:39 ` Thomas Huth
2023-02-28 9:01 ` Daniel P. Berrangé
2023-02-28 11:46 ` Michael S. Tsirkin
2023-02-28 20:05 ` Thomas Huth
2023-02-28 21:32 ` Michael S. Tsirkin
2023-03-01 6:38 ` Thomas Huth
2023-03-01 7:35 ` Markus Armbruster
2023-03-01 7:46 ` Warner Losh
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=87h6v6gh1g.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=libvir-list@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mlevitsk@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=reinoud@netbsd.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.com \
--cc=xen-devel@lists.xenproject.org \
/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.