Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler via Gdb" <gdb@sourceware.org>
To: Overseers mailing list <overseers@sourceware.org>
Cc: gcc@gcc.gnu.org, libc-alpha@sourceware.org,
	Siddhesh Poyarekar <siddhesh@gotplt.org>,
	gdb@sourceware.org, Mark Wielaard <mark@klomp.org>,
	binutils@sourceware.org
Subject: Re: The GNU Toolchain Infrastructure Project
Date: Thu, 6 Oct 2022 17:36:21 -0400	[thread overview]
Message-ID: <20221006213621.GA17528@redhat.com> (raw)
In-Reply-To: <f9025462-4a41-3991-22fd-7b4da598d922@gotplt.org>

Hi -

> [...] Or alternatively, "sourceware overseers" could become a body
> that maintains sourceware and is able to get funding through SFC for
> its activities?

Great idea -- and this is roughly what's happening.  This "body"
consisting of key individuals has invited other folks interested in
helping with or helping guide the upkeep of shared sourceware
infrastructure to join us.

- FChE


  reply	other threads:[~2022-10-06 21:36 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d9cb6cf9-89f5-87bb-933b-a03240479e71@redhat.com>
     [not found] ` <a9396df3-5699-46ef-0b33-6c7589274654@redhat.com>
2022-10-02 20:47   ` Mark Wielaard
2022-10-04 13:46     ` Siddhesh Poyarekar
2022-10-04 14:01       ` Frank Ch. Eigler via Gdb
2022-10-04 14:13         ` Siddhesh Poyarekar
2022-10-04 14:19           ` Frank Ch. Eigler via Gdb
2022-10-04 14:33             ` Siddhesh Poyarekar
2022-10-04 14:41               ` Frank Ch. Eigler via Gdb
2022-10-04 14:55                 ` Siddhesh Poyarekar
2022-10-04 15:07                   ` Frank Ch. Eigler via Gdb
2022-10-06 21:42             ` Alexandre Oliva via Gdb
2022-10-04 17:10       ` Christopher Faylor via Gdb
2022-10-04 17:17         ` Siddhesh Poyarekar
2022-10-04 18:42           ` Christopher Faylor via Gdb
2022-10-04 19:05           ` Mark Wielaard
2022-10-04 19:10             ` Siddhesh Poyarekar
2022-10-06 20:02               ` Mark Wielaard
2022-10-06 20:12                 ` Christopher Faylor via Gdb
2022-10-06 21:37                   ` Siddhesh Poyarekar
2022-10-07 13:39                     ` Mark Wielaard
2022-10-06 21:07                 ` Siddhesh Poyarekar
2022-10-06 21:36                   ` Frank Ch. Eigler via Gdb [this message]
2022-10-06 21:44                     ` Siddhesh Poyarekar
2022-10-06 22:57                       ` Frank Ch. Eigler via Gdb
2022-10-11 13:02                         ` Siddhesh Poyarekar
2022-10-07  8:57                   ` Mark Wielaard
2022-10-11 13:24                     ` Siddhesh Poyarekar
2022-10-11 14:23                       ` Frank Ch. Eigler via Gdb
2022-10-11 15:58                     ` Alexandre Oliva via Gdb
2022-10-11 17:14                       ` David Edelsohn via Gdb
2022-10-11 18:12                         ` Frank Ch. Eigler via Gdb
2022-10-12  8:00                         ` Mark Wielaard
2022-10-12 13:18                           ` Florian Weimer via Gdb
2022-10-12 21:23                             ` Mark Wielaard
2022-10-12 15:15                           ` Jonathan Corbet
2022-10-12 10:55                         ` Alexandre Oliva via Gdb
     [not found] <b00dc0aa-31a6-a004-a430-099af3d0f6d1@redhat.com>
     [not found] ` <558996ac-e4a0-cf77-48b9-f7d0e13862e8@redhat.com>
2022-10-17 11:48   ` Luis Machado via Gdb
2022-10-17 12:08     ` Siddhesh Poyarekar
2022-10-17 12:16       ` Luis Machado via Gdb
2022-10-18 18:45         ` Siddhesh Poyarekar
2022-09-27 20:08 Carlos O'Donell via Gdb
2022-09-28 22:38 ` 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=20221006213621.GA17528@redhat.com \
    --to=gdb@sourceware.org \
    --cc=binutils@sourceware.org \
    --cc=fche@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=libc-alpha@sourceware.org \
    --cc=mark@klomp.org \
    --cc=overseers@sourceware.org \
    --cc=siddhesh@gotplt.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