mailing list of musl libc
 help / color / mirror / code / Atom feed
From: "(GalaxyMaster)" <>
Subject: Re: [musl] musl -- FFS get your shit together, please
Date: Mon, 17 Jul 2023 07:20:36 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>


> On 17 Jul 2023, at 16:17, Dave Blanchard <> wrote:
> There's a lot to like about musl, but damn, there's some absolutely ridiculous aspects also:
> Musl is clearly not designed with Linux workstation usage in mind!

I understand that you've hit some frustration point whether it was triggered by a change in musl or not, but it does not help anyone to start a message in an offensive tone and basically call everyone in the community morons.  Nobody is forcing you to use the open source software (such as musl) and the majority of people are just grateful that there are people who are spending their spare time to improve a project in meaningful ways.

I would suggest to take a walk and calm down a bit when you are getting to agitated, then you can produce a message that contributes in a positive way and does not offend people.  Believe me, it is a win-win for everybody in this case.


  reply	other threads:[~2023-07-17 10:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-17  6:17 Dave Blanchard
2023-07-17  7:20 ` (GalaxyMaster) [this message]
2023-07-17 12:14 ` Daniel Gutson
2023-07-17 15:21 ` Rich Felker
2023-07-17 15:43   ` [musl] ITT: Nothing but a bunch of excuses and no solutions Dave Blanchard
2023-07-17 15:50     ` Joakim Sindholt
2023-07-17 17:12     ` Rich Felker
2023-07-17 17:23     ` Laurent Bercot
2023-07-17 16:01   ` [musl] musl -- FFS get your shit together, please Jeffrey Walton
2023-07-17 16:10     ` Joakim Sindholt
2023-07-17 16:55     ` Rich Felker
2023-07-17 15:32 ` Markus Wichmann

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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).