Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Zack Weinberg via Gdb <gdb@sourceware.org>
To: "Carlos O'Donell" <carlos@redhat.com>,
	libc-alpha <libc-alpha@sourceware.org>,
	"gcc developers" <gcc@gcc.gnu.org>,
	"gdb developers" <gdb@sourceware.org>,
	"binutils developers" <binutils@sourceware.org>
Subject: Re: Meeting Minutes - Office Hours for CTI - 2026-09-04
Date: Sun, 06 Sep 2026 11:32:45 -0400	[thread overview]
Message-ID: <e1a6dc08-e344-434e-a0e5-bd9f4ec72041@app.fastmail.com> (raw)
In-Reply-To: <3cdd6469-b1c8-464c-939b-f1d454c6dad8@redhat.com>

On Fri, Sep 4, 2026, at 5:36 PM, Carlos O'Donell wrote:
> CTI: https://cti.coretoolchain.dev/
>
> The CTI project holds Office Hours every Friday, these are the minutes
> for this Friday's meeting.

Once again I must ask that you stop holding synchronous meetings. Your
insistence on making decisions in synchronous meetings is a major
contributing factor to why CTI's proposed infrastructure changes have
been and are continuing to be so very contentious.

It may be helpful to spin up a new dedicated mailing list, instead, but
as long as major, disruptive, hotly contended transitions are on the
table, all of the potentially affected projects' main mailing lists need
to be cc:ed on *every message*.

For closely related reasons, please post the *full text* of all the
documents you linked from your minutes *directly to the mailing lists*,
so that there is a permanent record of what those documents said at the
time you linked to them.

zw

      parent reply	other threads:[~2026-09-06 15:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 21:36 Carlos O'Donell via Gdb
2026-09-04 21:43 ` Andrew Pinski via Gdb
2026-09-06 15:32 ` Zack Weinberg via Gdb [this message]

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=e1a6dc08-e344-434e-a0e5-bd9f4ec72041@app.fastmail.com \
    --to=gdb@sourceware.org \
    --cc=binutils@sourceware.org \
    --cc=carlos@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=libc-alpha@sourceware.org \
    --cc=zack@owlfolio.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