From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: "Overseers mailing list" <overseers@sourceware.org>,
gdb@sourceware.org, libc-alpha@sourceware.org,
binutils@sourceware.org, gcc@gcc.gnu.org,
"Zoë Kooyman" <zoe@fsf.org>
Subject: Re: Toolchain Infrastructure project statement of support
Date: Fri, 14 Oct 2022 08:33:20 -0400 [thread overview]
Message-ID: <4f422ac7-c678-b8a7-aac7-0790e13adf7b@gotplt.org> (raw)
In-Reply-To: <20221013182529.sm76fysq37sv754x@cgf.cx>
On 2022-10-13 14:25, Christopher Faylor via Overseers wrote:
> Also, the FSF, being the existing fiscal sponsor to these projects,
> surely needs to review the formal agreements before we sunset our
> infrastructural offerings to glibc, gcc, binutils, and gdb and hand
> control of the projects' infrastructure over to a different entity.
I believe Nick at least has said that for binutils they would like to
use both, i.e. mirror some of the LF offerings with sourceware (or vice
versa, I suppose it's Nick's call to take) and that'll probably be the
case for glibc and gcc as well over the years. So sunset, whenever that
will be and whatever it'll look like, will likely be a while.
Sid
next prev parent reply other threads:[~2022-10-14 12:33 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 16:43 Carlos O'Donell
2022-10-12 18:13 ` Andrew Pinski
2022-10-13 18:25 ` Christopher Faylor
2022-10-14 12:33 ` Siddhesh Poyarekar [this message]
2022-10-17 15:10 ` Mark Wielaard
2022-10-17 16:11 ` Siddhesh Poyarekar
2022-10-18 9:50 ` Mark Wielaard
2022-10-18 15:17 ` Siddhesh Poyarekar
2022-10-18 16:42 ` Christopher Faylor
2022-10-18 18:13 ` Siddhesh Poyarekar
2022-10-18 18:14 ` Siddhesh Poyarekar
2022-10-18 18:47 ` Paul Smith
2022-10-21 0:33 ` Alexandre Oliva
2022-10-23 8:59 ` Ian Kelling
2022-10-23 13:27 ` Siddhesh Poyarekar
2022-10-23 15:16 ` Frank Ch. Eigler
2022-10-23 16:07 ` Siddhesh Poyarekar
2022-10-23 16:32 ` Siddhesh Poyarekar
2022-10-23 17:01 ` Jeff Law
2022-10-23 22:35 ` Christopher Faylor
2022-10-23 17:09 ` Frank Ch. Eigler
2022-10-23 17:38 ` Jeff Law
2022-10-24 1:51 ` Siddhesh Poyarekar
2022-10-24 12:40 ` Corinna Vinschen
2022-10-23 20:57 ` Christopher Faylor
2022-10-23 21:17 ` Siddhesh Poyarekar
2022-10-23 21:59 ` Christopher Faylor
2022-10-24 1:29 ` Siddhesh Poyarekar
2022-10-23 11:33 ` Ian Kelling
2022-10-23 16:17 ` Siddhesh Poyarekar
2022-10-23 18:56 ` Konstantin Ryabitsev
2022-10-23 21:19 ` Alexandre Oliva
2022-10-23 22:07 ` Christopher Faylor
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=4f422ac7-c678-b8a7-aac7-0790e13adf7b@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=libc-alpha@sourceware.org \
--cc=overseers@sourceware.org \
--cc=zoe@fsf.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).