public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Mark Wielaard <mark@klomp.org>, David Edelsohn <dje.gcc@gmail.com>
Cc: gcc@gcc.gnu.org,
	Overseers mailing list <overseers@sourceware.org>,
	libc-alpha@sourceware.org, gdb@sourceware.org,
	binutils@sourceware.org
Subject: Re: The GNU Toolchain Infrastructure Project
Date: Wed, 12 Oct 2022 09:15:12 -0600	[thread overview]
Message-ID: <87a661kr9b.fsf@meer.lwn.net> (raw)
In-Reply-To: <Y0Z0E2NszSi0mmbB@wildebeest.org>

Mark Wielaard <mark@klomp.org> writes:

> Then lets just let the past be the past. Now that the proposal is
> public lets discuss it publicly. There have been various question
> about the details on the overseers list. Lets just discuss those and
> see how we can move forward.

Along those lines, I asked a few questions back in September:

  https://sourceware.org/pipermail/overseers/2022q3/018906.html

They seem relevant for anybody wanting to understand this proposal, and
the answers should be at the fingertips of the people putting it
together.  Any chance the rest of us could be enlightened?

Thanks,

jon

  parent reply	other threads:[~2022-10-12 15:15 UTC|newest]

Thread overview: 54+ 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
2022-10-04 14:13         ` Siddhesh Poyarekar
2022-10-04 14:19           ` Frank Ch. Eigler
2022-10-04 14:33             ` Siddhesh Poyarekar
2022-10-04 14:41               ` Frank Ch. Eigler
2022-10-04 14:55                 ` Siddhesh Poyarekar
2022-10-04 15:07                   ` Frank Ch. Eigler
2022-10-06 21:42             ` Alexandre Oliva
2022-10-04 17:10       ` Christopher Faylor
2022-10-04 17:17         ` Siddhesh Poyarekar
2022-10-04 18:42           ` Christopher Faylor
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
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
2022-10-06 21:44                     ` Siddhesh Poyarekar
2022-10-06 22:57                       ` Frank Ch. Eigler
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
2022-10-11 15:58                     ` Alexandre Oliva
2022-10-11 17:14                       ` David Edelsohn
2022-10-11 18:12                         ` Frank Ch. Eigler
2022-10-12  8:00                         ` Mark Wielaard
2022-10-12 13:18                           ` Florian Weimer
2022-10-12 21:23                             ` Mark Wielaard
2022-10-12 15:15                           ` Jonathan Corbet [this message]
2022-10-12 10:55                         ` Alexandre Oliva
     [not found] <b00dc0aa-31a6-a004-a430-099af3d0f6d1@redhat.com>
     [not found] ` <558996ac-e4a0-cf77-48b9-f7d0e13862e8@redhat.com>
2022-10-02 20:54   ` Mark Wielaard
2022-10-03 19:24   ` Carlos O'Donell
2022-09-27 19:59 Carlos O'Donell
2022-09-28 14:06 ` Frank Ch. Eigler
2022-09-29  9:51 ` Mark Wielaard
2022-09-29 14:45 ` Jonathan Corbet
2022-09-29 17:13   ` Joseph Myers
2022-09-29 18:40     ` Elena Zannoni
2022-09-29 18:54     ` Andrew Pinski
2022-10-19  5:47   ` Carlos O'Donell
2022-09-29 21:13 ` Andrew Pinski
2022-09-30 14:35   ` Siddhesh Poyarekar
2022-09-30 15:05     ` Andrew Pinski
2022-09-30 15:51       ` Siddhesh Poyarekar
2022-10-02 21:56         ` Mark Wielaard
2022-09-30 15:22     ` Christopher Faylor
2022-09-30 15:34       ` Siddhesh Poyarekar
2022-10-02 21:38   ` Mark Wielaard
2022-10-02 22:19 ` Mark Wielaard

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=87a661kr9b.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=binutils@sourceware.org \
    --cc=dje.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=libc-alpha@sourceware.org \
    --cc=mark@klomp.org \
    --cc=overseers@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).