qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Andrew Randrianasulu" <randrianasulu@gmail.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	qemu-discuss@nongnu.org,
	"QEMU Developers" <qemu-devel@nongnu.org>,
	"Markus Armbruster" <armbru@redhat.com>
Subject: Re: dropping 32-bit host support
Date: Thu, 16 Mar 2023 14:32:15 +0100	[thread overview]
Message-ID: <0e06c704-40d7-b511-8353-0218c3d45d3b@redhat.com> (raw)
In-Reply-To: <CA+rFky6hnaCxF10ST=qsLsBjH6=M__kQPA=yoZhdCoB8sH96ug@mail.gmail.com>

On 16/03/2023 14.01, Andrew Randrianasulu wrote:
...
> Well, this language about "market" and "investment"  not just figures of the 
> speech, sadly? Because paid developers work on  areas they paid to develop, 
> by boss with big bucks.

Sorry for getting more explicit now, but: Can you please stop making such 
aggressive assertions which are obviously wrong and where you apparently 
have no clue about about?

If you'd followed the QEMU project, you'd know that there are very helpful 
people around, from all kind of companies, Linaro guys who help with 
reviewing and merging non-ARM patches, Red Hatters who help with BSD and 
Haiku patches, etc.

Anyway, if you're not happy with the way the project is evolving, then start 
contributing instead of grumbling.

  Thomas



  reply	other threads:[~2023-03-16 13:33 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 [this message]
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
     [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=0e06c704-40d7-b511-8353-0218c3d45d3b@redhat.com \
    --to=thuth@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-discuss@nongnu.org \
    --cc=randrianasulu@gmail.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).