Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Pinski via Gdb <gdb@sourceware.org>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: glibc developers <libc-alpha@sourceware.org>,
	gdb developers <gdb@sourceware.org>
Subject: Re: Nominations for Anthropic’s Claude for Open Source program
Date: Fri, 12 Jun 2026 14:21:20 -0700	[thread overview]
Message-ID: <CA+=Sn1nZvm6kcVWjysSS+N7-dTfasnrJRDCVnJ+BhqQhVwboOQ@mail.gmail.com> (raw)
In-Reply-To: <016af9e2-eff9-427d-ae92-fe6f02d91f77@redhat.com>

On Fri, Jun 12, 2026 at 2:18 PM Carlos O'Donell <carlos@redhat.com> wrote:
>
> On 6/12/26 3:29 PM, Andrew Pinski wrote:
> > Dont send out emails like this in the first place then.
> >
> > Also note coverity has been offering similar services for code
> > coverage and static analysis for years now. But there was no notice
> > like that sent out for this. Why try to push llm when static
> > analysis does the same?
>
> Coverity FOSS scanning of glibc has been in the release process
> for almost 11 years [1][2][3].
>
> Emails to this list are permitted so long as they are on topic,
> and meet the community code of conduct.
>
> Asking politely to stay on topic is appropriate.
>
> Telling the community what it should or should not do is not
> called for.

And your email is telling the community it should be NOT talking about
the ethics here.
So you just violated your own writing.

>
> --
> Cheers,
> Carlos.
>
> [1] https://inbox.sourceware.org/libc-alpha/443E97C6.2080801@coverity.com/
> [2] https://inbox.sourceware.org/libc-alpha/55DFBA26.2000601@redhat.com/
> [3] https://sourceware.org/glibc/wiki/Coverity
>

  reply	other threads:[~2026-06-12 21:22 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 [this message]
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
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='CA+=Sn1nZvm6kcVWjysSS+N7-dTfasnrJRDCVnJ+BhqQhVwboOQ@mail.gmail.com' \
    --to=gdb@sourceware.org \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=pinskia@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