Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Alexandre Oliva via Gdb <gdb@sourceware.org>
To: David Edelsohn <dje.gcc@gmail.com>
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: The GNU Toolchain Infrastructure Project
Date: Wed, 12 Oct 2022 07:55:30 -0300	[thread overview]
Message-ID: <or5ygpnwf1.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <CAGWvnykKOF=A=LWJ=Rozqx03w3YoCaP+yZ3L8X5+9MFgJ3MO-g@mail.gmail.com> (David Edelsohn's message of "Tue, 11 Oct 2022 13:14:50 -0400")

On Oct 11, 2022, David Edelsohn <dje.gcc@gmail.com> wrote:

> open and available for conversations to clarify misunderstandings

Not useful when potential objectors are kept in the dark about the whole
thing.

> and have not used private conversations as public debating points nor for
> divisive purposes

The public claims of broad support used to put pressure for objectors to
give in seem to fit this pattern you deny, if not so much in seeding the
divide created by the then-secret proposal, but in bridging it.

The very purpose of private conversations was claimed by proponents of
the conversation as something to the effect of avoiding objections.

As for purporting key decisions as if in the hands of an advisory
committee, while the final decisions would rest in the hands of another
body whose members would be effectively buying the projects on the
cheap...

All of that, too, speaks for itself.


Anyway, this is all besides the point.  Whether or not there are
nefarious purposes behind it is besides the point.  The key point I
raise is that most people would support and accept something desirable
offered to them at no charge, but many might not upon finding that
there's a very steep price involved in the transaction.  There's no
evidence whatsoever that the costs have been conveyed along with the
dreams to the supposed supporters, so we'd better not take that alleged
support for granted.  The whole process was structured in a certain way,
explicitly for the purpose of sidelining objections.  That does not
inspire the very trust that would be required to agree to turn over
control over our infrastructure.

-- 
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-12 10:56 UTC|newest]

Thread overview: 41+ 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 via Gdb
2022-10-04 14:13         ` Siddhesh Poyarekar
2022-10-04 14:19           ` Frank Ch. Eigler via Gdb
2022-10-04 14:33             ` Siddhesh Poyarekar
2022-10-04 14:41               ` Frank Ch. Eigler via Gdb
2022-10-04 14:55                 ` Siddhesh Poyarekar
2022-10-04 15:07                   ` Frank Ch. Eigler via Gdb
2022-10-06 21:42             ` Alexandre Oliva via Gdb
2022-10-04 17:10       ` Christopher Faylor via Gdb
2022-10-04 17:17         ` Siddhesh Poyarekar
2022-10-04 18:42           ` Christopher Faylor via Gdb
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 via Gdb
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 via Gdb
2022-10-06 21:44                     ` Siddhesh Poyarekar
2022-10-06 22:57                       ` Frank Ch. Eigler via Gdb
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 via Gdb
2022-10-11 15:58                     ` Alexandre Oliva via Gdb
2022-10-11 17:14                       ` David Edelsohn via Gdb
2022-10-11 18:12                         ` Frank Ch. Eigler via Gdb
2022-10-12  8:00                         ` Mark Wielaard
2022-10-12 13:18                           ` Florian Weimer via Gdb
2022-10-12 21:23                             ` Mark Wielaard
2022-10-12 15:15                           ` Jonathan Corbet
2022-10-12 10:55                         ` Alexandre Oliva via Gdb [this message]
     [not found] <b00dc0aa-31a6-a004-a430-099af3d0f6d1@redhat.com>
     [not found] ` <558996ac-e4a0-cf77-48b9-f7d0e13862e8@redhat.com>
2022-10-17 11:48   ` Luis Machado via Gdb
2022-10-17 12:08     ` Siddhesh Poyarekar
2022-10-17 12:16       ` Luis Machado via Gdb
2022-10-18 18:45         ` Siddhesh Poyarekar
2022-09-27 20:08 Carlos O'Donell via Gdb
2022-09-28 22:38 ` 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=or5ygpnwf1.fsf@lxoliva.fsfla.org \
    --to=gdb@sourceware.org \
    --cc=binutils@sourceware.org \
    --cc=dje.gcc@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=libc-alpha@sourceware.org \
    --cc=mark@klomp.org \
    --cc=oliva@gnu.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