Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrea Pinski via Gdb <gdb@sourceware.org>
To: DJ Delorie <dj@redhat.com>
Cc: Joseph Myers <josmyers@redhat.com>,
	"Carlos O'Donell" <carlos@redhat.com>,
	 gcc developers <gcc@gcc.gnu.org>,
	glibc developers <libc-alpha@sourceware.org>,
	gdb developers <gdb@sourceware.org>,
	binutils developers <binutils@sourceware.org>
Subject: Re: Meeting Minutes - Office Hours for CTI - 2026-09-18
Date: Tue, 22 Sep 2026 12:22:13 -0700	[thread overview]
Message-ID: <CALvbMcAupz_NUD_wSYaZP_yXs5TtLgJ1Y1MztWyy3nF=LS0v6Q@mail.gmail.com> (raw)
In-Reply-To: <CA+J5ysMf_RXjL4nvu3UJLre0t=4SEjJ6X13_a5pAcsWu_uCabA@mail.gmail.com>

On Tue, Sep 22, 2026 at 12:14 PM DJ Delorie <dj@redhat.com> wrote:
>
> On Tue, Sep 22, 2026 at 3:03 PM Andrea Pinski via Binutils
> <binutils@sourceware.org> wrote:
> > So there was no consensus on the community members except for the ones
> > who were at the meeting?
>
> You would prefer "so there was no consensus except for the ones who
> were on the mailing list" ?
>
> Carlos and Mark have both been diligent in announcing these meetings
> and posting minutes.  If you choose to ignore them, that's on you.

Hmm, no carlos has been diligent in announcing the meetings.  Also it
conflicts with many other meetings I have.  And it is NOT a time that
is viable for me.
So I have not chosen to ignore them.  And now you are dictating how
this consensus should be brought together in the same way you mention
Zack is doing.

>
> > Ok. I think that it is wrong to have separate domains.
>
> I think it's inevitable.
>
> > Also why NOT just one email list?  Why 6 mailing lists?
>
> Why not 47?  Why not zero?  If you have a specific request, please
> make it and justify it.  We have an *opportunity* to reorganize
> mailing lists if/when we move the mail servers, but we *can*
> reorganize the lists any time we want, too.

Right and that is my point this should be a separate unrelated
discussion rather there are many different discussions going on and
things are being tied to the move for no reason.

>
> > What is the need for glibc-stable?
>
> Downstream maintainers who need to watch for bugfixes.  I would hope
> by now everyone would know this.

Why not just use -announcement for that?

>

  reply	other threads:[~2026-09-22 19:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 16:32 Carlos O'Donell via Gdb
2026-09-21 16:55 ` Andrea Pinski via Gdb
2026-09-21 17:58   ` DJ Delorie via Gdb
2026-09-22 18:14     ` Siddhesh Poyarekar
2026-09-22  9:46   ` Mark Wielaard
2026-09-22 18:34   ` Joseph Myers via Gdb
2026-09-22 19:02     ` Andrea Pinski via Gdb
2026-09-22 19:14       ` DJ Delorie via Gdb
2026-09-22 19:22         ` Andrea Pinski via Gdb [this message]
2026-09-24 14:55           ` Siddhesh Poyarekar
2026-09-22 20:37       ` Joseph Myers via Gdb
2026-09-23 15:58       ` Mark Wielaard
2026-09-24 15:15       ` Siddhesh Poyarekar
2026-09-24 15:21         ` Siddhesh Poyarekar
2026-09-25 21:28         ` Carlos O'Donell 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='CALvbMcAupz_NUD_wSYaZP_yXs5TtLgJ1Y1MztWyy3nF=LS0v6Q@mail.gmail.com' \
    --to=gdb@sourceware.org \
    --cc=andrew.pinski@oss.qualcomm.com \
    --cc=binutils@sourceware.org \
    --cc=carlos@redhat.com \
    --cc=dj@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=josmyers@redhat.com \
    --cc=libc-alpha@sourceware.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