Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Alexandre Oliva via Gdb <gdb@sourceware.org>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>
Cc: gcc@gcc.gnu.org,
	Overseers mailing list <overseers@sourceware.org>,
	libc-alpha@sourceware.org, gdb@sourceware.org,
	Mark Wielaard <mark@klomp.org>,
	binutils@sourceware.org
Subject: Re: Toolchain Infrastructure project statement of support
Date: Thu, 20 Oct 2022 21:33:44 -0300	[thread overview]
Message-ID: <orzgdqkobb.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <290f80c3-abb4-2f35-f933-066856542a02@gotplt.org> (Siddhesh Poyarekar's message of "Tue, 18 Oct 2022 14:13:21 -0400")

On Oct 18, 2022, Siddhesh Poyarekar <siddhesh@gotplt.org> wrote:

> 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.

So in which category do you place my question about the viability of
using the funds raised through the LF to pay for IT services provided by
third parties rather than by the LF?

-- 
Alexandre Oliva, happy hacker                https://FSFLA.org/blogs/lxo/
   Free Software Activist                       GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts.  Ask me about <https://stallmansupport.org>

  parent reply	other threads:[~2022-10-21  0:34 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 via Gdb
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 via Gdb
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 via Gdb [this message]
2022-10-23  8:59           ` Ian Kelling via Gdb
2022-10-23 13:27             ` Siddhesh Poyarekar
2022-10-23 15:16               ` Frank Ch. Eigler via Gdb
2022-10-23 16:07                 ` Siddhesh Poyarekar
2022-10-23 16:32                   ` Siddhesh Poyarekar
2022-10-23 17:01                   ` Jeff Law via Gdb
2022-10-23 22:35                     ` Christopher Faylor via Gdb
2022-10-23 17:09                   ` Frank Ch. Eigler via Gdb
2022-10-23 17:38                     ` Jeff Law via Gdb
2022-10-24  1:51                     ` Siddhesh Poyarekar
2022-10-23 20:57               ` Christopher Faylor via Gdb
2022-10-23 21:17                 ` Siddhesh Poyarekar
2022-10-23 21:59                   ` Christopher Faylor via Gdb
2022-10-24  1:29                     ` Siddhesh Poyarekar
2022-10-23 11:33       ` Ian Kelling via Gdb
2022-10-23 16:17         ` Siddhesh Poyarekar
2022-10-23 18:56           ` Konstantin Ryabitsev via Gdb
2022-10-23 21:19 ` Alexandre Oliva via Gdb
2022-10-23 22:07   ` Christopher Faylor via Gdb
2022-10-12 17:40 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=orzgdqkobb.fsf@lxoliva.fsfla.org \
    --to=gdb@sourceware.org \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=libc-alpha@sourceware.org \
    --cc=mark@klomp.org \
    --cc=oliva@gnu.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