public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dave Blanchard <dave@killthe.net>
To: gcc@gcc.gnu.org
Subject: Re: Good grief Charlie Brown
Date: Tue, 13 Dec 2022 13:29:11 -0600	[thread overview]
Message-ID: <20221213132911.c614d7c0d4835f3ee1432b59@killthe.net> (raw)
In-Reply-To: <B41C9027-DD88-4290-BC5E-3D9AB1022CA4@comcast.net>

On Tue, 13 Dec 2022 14:20:39 -0500
Paul Koning <paulkoning@comcast.net> wrote:

> I'm puzzled.  What is your purpose?  What result do you expect from your messages?  What action would you like to see?

GCC is a "mailing list." This is a recent innovation in which people post comments about subjects they are interested in discussing, and others submit replies on response. 

My message was a reply in one of those ongoing conversations entitled "Good grief Charlie Brown", in which OP laments certain design decisions the GCC project was made.

A response was made to his post, containing a counter-argument.

My response to that response contained my own counter-counter-argument.

Understand?

> I see some vague hints that there are some issues. 

Really? So you are vaguely aware that the GNU/Glibc/GCC bootstrap process is insanely brittle and broken?

> If you want those to be addressed, you should report them as defects through the bug tracker.  To do so, you should be specific as to what's failing so others can reproduce what you did and see what goes wrong.

So what should be the title of this issue--"your software is insanely broken and buggy and basically needs a partial or complete redesign"? OK. When should I expect resolution of this issue?

> Apart from that, generic "I don't like what you guys did" is obviously just going to get ignored as meaningless ravings.

And this should be considered surprising, considering GNU's long history of (seemingly on purpose) releasing junkware, despite user complaints?

Hell, I haven't even got started complaining about anything. Should we get into The Entire Linux Ecosystem, Led By GNU's recent bizarre decision to start incrementing major version numbers seemingly every 3 months? It's almost like you have forgotten every lesson you've ever learned about how to version software releases.

Dave

  reply	other threads:[~2022-12-13 19:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-13 19:09 Dave Blanchard
2022-12-13 19:20 ` Paul Koning
2022-12-13 19:29   ` Dave Blanchard [this message]
2022-12-13 20:35     ` Jonathan Wakely
  -- strict thread matches above, loose matches on Subject: below --
2022-12-13 16:28 Jim Anderson
2022-12-13 16:41 ` Paul Smith
2022-12-13 17:35   ` Dave Blanchard
2022-12-13 18:31     ` Paul Smith
2022-12-13 19:16 ` Dave Blanchard

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=20221213132911.c614d7c0d4835f3ee1432b59@killthe.net \
    --to=dave@killthe.net \
    --cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).