From: Jeff Law <jeffreyalaw@gmail.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
"Frank Ch. Eigler" <fche@redhat.com>,
Overseers mailing list <overseers@sourceware.org>
Cc: gcc@gcc.gnu.org, libc-alpha@sourceware.org, gdb@sourceware.org,
Mark Wielaard <mark@klomp.org>,
binutils@sourceware.org, Ian Kelling <iank@fsf.org>
Subject: Re: Toolchain Infrastructure project statement of support
Date: Sun, 23 Oct 2022 11:01:34 -0600 [thread overview]
Message-ID: <b6fc7aa6-ce06-8ea7-61a6-7932a1e4da0d@gmail.com> (raw)
In-Reply-To: <0bac951e-8f5e-deb6-c126-26d5fbd0bbfe@gotplt.org>
On 10/23/22 10:07, Siddhesh Poyarekar wrote:
>> If you're trying to suggest that overseers, contrary to our repeated
>> public statements, wish to block all migration, that is untrue and you
>> will need to retract this.
>
> Here's a more precise statement: Two of the overseers are leaders of
> projects hosted on sourceware and three overseers (including those
> two) have stated clearly on multiple occasions that transitioning to
> LF IT is off the table, effectively announcing their decision on
> behalf of projects they lead. It is hence clear that the overseers
> have effectively blocked full migration of sourceware to LF IT.
They can make those decisions for the projects they lead. But making
the decision or setting criteria for other projects is highly unreasonable.
Jeff
next prev parent reply other threads:[~2022-10-23 17:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2513b668-9ebd-9e78-7263-dc24f4a9558a@redhat.com>
2022-10-13 18:25 ` Christopher Faylor
2022-10-14 12:33 ` Siddhesh Poyarekar
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 [this message]
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-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
2022-10-12 17:40 Carlos O'Donell
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=b6fc7aa6-ce06-8ea7-61a6-7932a1e4da0d@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=binutils@sourceware.org \
--cc=fche@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=iank@fsf.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).