Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Carlos O'Donell via Gdb <gdb@sourceware.org>
To: Mark Wielaard <mark@klomp.org>, Andrew Pinski <pinskia@gmail.com>,
	Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: glibc developers <libc-alpha@sourceware.org>,
	gdb developers <gdb@sourceware.org>,
	Jonathan Wakely <jwakely@redhat.com>
Subject: Re: Nominations for Anthropic’s Claude for Open Source program
Date: Fri, 19 Jun 2026 20:09:31 -0400	[thread overview]
Message-ID: <d2c558b2-3ca4-4e05-867a-a91294ff8a6c@redhat.com> (raw)
In-Reply-To: <5158b893-6bb4-4856-acc8-876157671f34@redhat.com>

On 6/15/26 5:11 PM, Carlos O'Donell wrote:
> On 6/15/26 7:39 AM, Mark Wielaard wrote:
> I will raise this with the WG lead Jonathan Wakely this Friday, and ask
> the WG's opinion if they believe I can be impartial.
This was raised as the first point of order in the GCC working group
for AI Policy chaired by Jonathan Wakely.

The Working Group reviewed the issue and decided I was able to
be impartial and continue my contribution to the policy.

-- 
Cheers,
Carlos.


  parent reply	other threads:[~2026-06-20  0:10 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 [this message]
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=d2c558b2-3ca4-4e05-867a-a91294ff8a6c@redhat.com \
    --to=gdb@sourceware.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=carlos@redhat.com \
    --cc=jwakely@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=mark@klomp.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