public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 216026] Fails to compile using gcc 12.1 under Ubuntu 22.04
Date: Tue, 21 Jun 2022 05:46:02 +0000	[thread overview]
Message-ID: <bug-216026-28872-erFiTXe83h@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216026-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=216026

--- Comment #34 from Robert Dinse (nanook@eskimo.com) ---
I'm all for honesty, not so much for brutality, but I do realize that many
people who work with computers choose to do so because they're not so good with
humans.

That said, your position would be appropriate if Linux were still Linus's hobby
project.

The reality is that much of the real world computation depends upon it, the
vast majority of super computers run Linux, Android phones run Linux, most of
Googles, Amazons, and even Microsoft's services run Linux, so it has grown
beyond hobby status.  Self driving cars depend upon it, etc.  In short, it is
critical to the technological world and technology is critical to 8 billion
people surviving on this ball we call Earth.  So this requires a bit more
professionalism than a hobby project.

Isn't my intent to spam a mailing list, it is my intent to make the developers
aware of a SERIOUS bug, and when a kernel can't be compiled with the most
recent versions of EITHER compiler chains, that is serious, especially when
you've End-of-Life'd the previous version which means they are not getting
security fixes.

I've been involved in some development projects myself, back in the days of
8-bit computers I even wrote a very specialized programming language, but I've
never worked with a team of more than half a dozen individuals, so I can't even
imagine what it is like for Linus to coordinate several thousand developers.

That said, personality issues don't help, best to stick with technical issues,
tackle them and move on.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-06-21  5:46 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-25  7:56 [Bug 216026] New: Fails to compile using gcc 12.1 under Ubuntu 22.04 bugzilla-daemon
2022-05-25  8:17 ` [Bug 216026] " bugzilla-daemon
2022-05-25  8:34 ` bugzilla-daemon
2022-05-25 15:59 ` bugzilla-daemon
2022-05-25 19:40 ` bugzilla-daemon
2022-05-25 20:51 ` bugzilla-daemon
2022-05-26  1:48 ` bugzilla-daemon
2022-05-27  0:52 ` bugzilla-daemon
2022-05-30 19:47 ` bugzilla-daemon
2022-05-30 19:57 ` bugzilla-daemon
2022-05-31  2:10 ` bugzilla-daemon
2022-05-31 10:42 ` bugzilla-daemon
2022-06-01  6:56 ` bugzilla-daemon
2022-06-01  7:04 ` bugzilla-daemon
2022-06-07  7:41 ` bugzilla-daemon
2022-06-07  8:54 ` bugzilla-daemon
2022-06-10 22:48 ` bugzilla-daemon
2022-06-13 15:16 ` bugzilla-daemon
2022-06-14 10:56 ` bugzilla-daemon
2022-06-15 14:05 ` bugzilla-daemon
2022-06-15 22:11 ` bugzilla-daemon
2022-06-15 22:17 ` bugzilla-daemon
2022-06-16 21:22 ` bugzilla-daemon
2022-06-16 21:25 ` bugzilla-daemon
2022-06-18 17:34 ` bugzilla-daemon
2022-06-19  0:29 ` bugzilla-daemon
2022-06-19  0:30 ` bugzilla-daemon
2022-06-19  0:31 ` bugzilla-daemon
2022-06-20  4:35 ` bugzilla-daemon
2022-06-20  7:16 ` bugzilla-daemon
2022-06-20 13:39 ` bugzilla-daemon
2022-06-20 14:01 ` bugzilla-daemon
2022-06-20 14:33 ` bugzilla-daemon
2022-06-20 15:25 ` bugzilla-daemon
2022-06-21  5:46 ` bugzilla-daemon [this message]
2022-06-21 11:23 ` bugzilla-daemon
2022-06-21 16:05 ` bugzilla-daemon
2022-06-21 16:06 ` bugzilla-daemon
2022-06-21 21:45 ` bugzilla-daemon
2022-06-24  0:00 ` bugzilla-daemon
2022-06-26 19:04 ` bugzilla-daemon
2022-06-27  7:41 ` bugzilla-daemon
2022-06-27 14:21 ` bugzilla-daemon

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=bug-216026-28872-erFiTXe83h@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox