From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Mark Wielaard <mark@klomp.org>,
gdb@sourceware.org,
Overseers mailing list <overseers@sourceware.org>,
libc-alpha@sourceware.org, binutils@sourceware.org,
gcc@gcc.gnu.org
Subject: Re: Toolchain Infrastructure project statement of support
Date: Tue, 18 Oct 2022 14:13:21 -0400 [thread overview]
Message-ID: <290f80c3-abb4-2f35-f933-066856542a02@gotplt.org> (raw)
In-Reply-To: <20221018164201.22snv4zgbbobnzht@cgf.cx>
On 2022-10-18 12:42, Christopher Faylor wrote:
> On Tue, Oct 18, 2022 at 11:17:15AM -0400, Siddhesh Poyarekar wrote:
>> That is not true, Mark. Your objections and questions have been answered at
>> every stage, privately as well as publicly.
>
> Actually, going back through this thread, I see outstanding
> questions/issues raised by Mark, Frank, Alexandre Oliva, Jon Corbet, and
> Andrew Pinski.
As far as actual questions regarding the proposal is concerned, I think
only Job Corbet's questions to Carlos/David are pending an answer; I
deferred them to Carlos or David because I think they're better placed
to answer them in their entirety. The rest, AFAICT, are either fear of
some kind of corporate takeover, discussions about current sourceware
infrastructure, or just rhetoric, none of which I'm interested in
engaging with.
The corporate takeover fear especially is amusing to me given how much
of GNU toolchain development and infrastructure is sponsored by
corporations right now but that's just my personal opinion.
Maybe the FSF hosted call next week[1] would be a suitable forum to
discuss fears of corporate control of the GNU toolchain project
infrastructure due to the LF IT migration, or for that matter any other
questions you or others think may have gone unanswered. Since
sourceware is neither a GNU nor an FSF project, it probably does not
make sense to discuss current sourceware infrastructure there.
Sid
[1] https://sourceware.org/pipermail/overseers/2022q4/018997.html
next prev parent reply other threads:[~2022-10-18 18:13 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
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 [this message]
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=290f80c3-abb4-2f35-f933-066856542a02@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=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).