Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jeffrey Walton via Gdb <gdb@sourceware.org>
To: libc-alpha@sourceware.org
Cc: gdb@sourceware.org
Subject: Re: Nominations for Anthropic’s Claude for Open Source program
Date: Thu, 18 Jun 2026 10:44:39 -0400	[thread overview]
Message-ID: <CAH8yC8=v4KGUPBsEfDO8XsMjJ5OTgjJJDHHEugSbTJzL=ypCkA@mail.gmail.com> (raw)
In-Reply-To: <ora4ssyner.fsf@lxoliva.fsfla.org>

On Thu, Jun 18, 2026 at 9:44 AM Alexandre Oliva via Gdb
<gdb@sourceware.org> wrote:
>
> On Jun 18, 2026, Eli Zaretskii <eliz@gnu.org> wrote:
> [...]
>
> > I'm disputing your uncalled-for attack on David
>
> Erhm.  What attack?  There's no attack on David, or on Carlos, for that
> matter.  What I'm doing is call out the initiation of the threads as
> spam, and insisting that we shouldn't normalize or repeat that kind of
> post, because it would be detrimental to our shared goals.

Related (or maybe off-topic)...  I think this is one of the behavioral
attributes of Gen-Z and above.  The behavioral psychologists tell us
that kids raised on smartphones and social media can lack problem
resolution skills and they are hypersensitive to criticism.[1,2,3,4]
To them, nearly everyone who disagrees with them is an attack.  (Big
Tech acknowledges the problems, but disputes the cause).

[1] https://www.theatlantic.com/technology/archive/2024/03/teen-childhood-smartphone-use-mental-health-effects/677722/
[2] https://www.vox.com/24127431/smartphones-young-kids-children-parenting-social-media-teen-mental-health
[3] https://www.scientificamerican.com/article/social-media-algorithms-warp-how-people-learn-from-each-other/
[4] https://www.noemamag.com/social-media-messed-up-our-kids-now-it-is-making-us-ungovernable/

Jeff

  parent reply	other threads:[~2026-06-18 14:46 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-12 19:18 Carlos O'Donell via Gdb
2026-06-12 19:29 ` Andrew Pinski via Gdb
2026-06-12 21:18   ` Carlos O'Donell via Gdb
2026-06-12 21:21     ` Andrew Pinski via Gdb
2026-06-12 23:07   ` Adhemerval Zanella Netto via Gdb
2026-06-12 23:11     ` Andrew Pinski via Gdb
2026-06-15 11:39       ` Mark Wielaard
2026-06-15 21:11         ` Carlos O'Donell via Gdb
2026-06-16 11:03           ` Mark Wielaard
2026-06-16 13:53             ` Carlos O'Donell via Gdb
2026-06-17 16:28               ` Alexandre Oliva via Gdb
2026-06-18  5:27                 ` Eli Zaretskii via Gdb
2026-06-18  6:59                   ` Alexandre Oliva via Gdb
2026-06-18  7:41                     ` Eli Zaretskii via Gdb
2026-06-18 13:43                       ` Alexandre Oliva via Gdb
2026-06-18 14:11                         ` Eli Zaretskii via Gdb
2026-06-18 14:44                         ` Jeffrey Walton via Gdb [this message]
2026-06-18 17:11                   ` Thomas Dineen via Gdb
2026-06-19 22:21                     ` Andy Wang via Gdb
2026-06-16 16:03             ` Siddhesh Poyarekar
2026-06-20  0:09           ` Carlos O'Donell via Gdb
2026-06-15 17:25       ` Siddhesh Poyarekar
2026-06-12 23:46     ` Collin Funk via Gdb
2026-06-13  1:15       ` Sam James via Gdb
2026-06-15 21:17       ` Carlos O'Donell via Gdb
2026-06-15 21:35         ` Andrew Pinski via Gdb
2026-06-15 23:10           ` Adhemerval Zanella Netto via Gdb
2026-06-16 14:50             ` Xi Ruoyao via Gdb
2026-06-16 14:59               ` Adhemerval Zanella Netto via Gdb
2026-06-16 17:49                 ` Carlos O'Donell via Gdb
2026-06-22 18:35                   ` Gokhan via Gdb
2026-06-16 16:22             ` Joseph Myers via Gdb
2026-06-16 16:44               ` Collin Funk via Gdb
2026-06-12 23:12 ` Sam James via Gdb
2026-06-15 21:19   ` Carlos O'Donell via Gdb
2026-06-16 16:08     ` Siddhesh Poyarekar
2026-06-16 16:36       ` Joseph Myers via Gdb
2026-06-16 18:01         ` Carlos O'Donell via Gdb
2026-06-13  0:19 ` Alexandre Oliva via Gdb

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='CAH8yC8=v4KGUPBsEfDO8XsMjJ5OTgjJJDHHEugSbTJzL=ypCkA@mail.gmail.com' \
    --to=gdb@sourceware.org \
    --cc=libc-alpha@sourceware.org \
    --cc=noloader@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