From: Andrew Randrianasulu <randrianasulu@gmail.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-discuss@nongnu.org,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: dropping 32-bit host support
Date: Thu, 16 Mar 2023 13:05:04 +0300 [thread overview]
Message-ID: <CA+rFky5JchyFTEdYoGFezJzjnbS2MK_zUou4EME-uf-oBsp-YA@mail.gmail.com> (raw)
In-Reply-To: <878rfxuiau.fsf@pond.sub.org>
[-- Attachment #1: Type: text/plain, Size: 1254 bytes --]
чт, 16 мар. 2023 г., 13:01 Markus Armbruster <armbru@redhat.com>:
> Thomas Huth <thuth@redhat.com> writes:
>
> [...]
>
> > The problem is really that we don't have unlimited resources in the
> > QEMU project. Currently we're heavily struggling with the load in the
> > CI, but also pure man power is always very scarce. So at one point in
> > time, you have to decide to say good bye to some old and hardly used
> > features - at least to stop testing and actively supporting it. If you
> > want to continue testing and fixing bugs for such host systems, that's
> > fine, of course, but don't expect the QEMU developers to do that job
> > in the future.
>
> This.
>
> We're out of free lunch. We're glad you enjoyed it while it lasted.
>
> If you want more lunch, you need to join the kitchen. Here are a few
> things we need to keep a host or target supported:
>
> * Competent maintainer(s) to relieve the ones who have maintained this
> for you so far
>
> * CI runners to conserve scarce CI minutes (or the money to buy more)
>
> * Trustworthy system administrator(s) to set them up and keep them
> running.
>
* Four - different developer culture, like, a bit fewer commits to run CI
with ? :)
>
[-- Attachment #2: Type: text/html, Size: 2000 bytes --]
next prev parent reply other threads:[~2023-03-16 10:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+rFky6A9Q_5sJ4WDO-Z2HBT59qiNgr8A-xk+O7-gnAMZmHt2A@mail.gmail.com>
2023-03-16 7:05 ` dropping 32-bit host support Philippe Mathieu-Daudé
2023-03-16 7:17 ` Andrew Randrianasulu
2023-03-16 7:36 ` Philippe Mathieu-Daudé
2023-03-16 7:44 ` Andrew Randrianasulu
2023-03-16 8:31 ` Thomas Huth
2023-03-16 9:17 ` Andrew Randrianasulu
2023-03-16 10:22 ` Andrew Randrianasulu
2023-03-16 10:56 ` Philippe Mathieu-Daudé
2023-03-16 11:04 ` Andrew Randrianasulu
2023-03-16 11:15 ` Thomas Huth
2023-03-16 11:02 ` Thomas Huth
2023-03-16 11:11 ` Andrew Randrianasulu
2023-03-16 12:35 ` Daniel P. Berrangé
2023-03-16 13:01 ` Andrew Randrianasulu
2023-03-16 13:32 ` Thomas Huth
2023-03-16 15:21 ` Warner Losh
2023-03-16 15:29 ` Andrew Randrianasulu
2023-03-16 15:27 ` Andrew Randrianasulu
2023-03-16 15:39 ` Daniel P. Berrangé
2023-03-17 8:03 ` Andrew Randrianasulu
2023-03-16 10:00 ` Markus Armbruster
2023-03-16 10:05 ` Andrew Randrianasulu [this message]
[not found] ` <3DD8295F-4BE0-4262-8C68-4A85A56D63C7@livius.net>
2023-03-16 7:29 ` Philippe Mathieu-Daudé
2023-03-16 7:57 ` Liviu Ionescu
2023-03-16 8:07 ` Liviu Ionescu
2023-03-16 8:36 ` Thomas Huth
2023-03-16 8:42 ` Liviu Ionescu
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=CA+rFky5JchyFTEdYoGFezJzjnbS2MK_zUou4EME-uf-oBsp-YA@mail.gmail.com \
--to=randrianasulu@gmail.com \
--cc=armbru@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@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).