Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Andrew Pinski <pinskia@gmail.com>,
	Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: Carlos O'Donell <carlos@redhat.com>,
	glibc developers <libc-alpha@sourceware.org>,
	gdb developers <gdb@sourceware.org>
Subject: Re: Nominations for Anthropic’s Claude for Open Source program
Date: Mon, 15 Jun 2026 13:25:49 -0400	[thread overview]
Message-ID: <25ebff11-fa7d-4b58-94ec-37e0a01de9eb@gotplt.org> (raw)
In-Reply-To: <CA+=Sn1k0Ooe96oKt3fbm9R2CVwzF3spdGh-A3N-YEjac+zSi_w@mail.gmail.com>

On 12/06/2026 19:11, Andrew Pinski wrote:
> All of this talk about llm and llm reviews is off-topic for this list. Including the original email is off-topic and should not have been sent.

How so?  Adhemerval's comment mentioned LLM use for patch reviews in 
other GNU projects, which is useful information for this developer 
community.

>    Can you step down from the llm gcc working group for this email since 
> it shows a conflict of interest of prompting one product.  Plus it shows 
> poor taste of sending out an email about a non free product to a mailing 
> list about glibc development.
Visible maintainers of FOSS projects routinely get these kinds of offers 
upfront and forwarding them to community members IMO doesn't mean 
anything more than simply making others aware.  I don't see a conflict 
of interest here, but that's for the WG to decide.

Is this marketing for Anthropic?  Yes, and it is the right of the 
members of this community to reject it outright, or use it to experiment 
if they wish to, without contributing AI generated legally significant 
code to the project.

FWIW, I have a strong personal preference against using frontier LLMs. 
Maybe I'm more acceptable as a LLM WG member because I align with your 
position? ;)

Sid

  parent reply	other threads:[~2026-06-15 17:26 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
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 [this message]
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=25ebff11-fa7d-4b58-94ec-37e0a01de9eb@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.com \
    --cc=gdb@sourceware.org \
    --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