From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <kenner@vlsi1.ultra.nyu.edu>
Received: from vlsi1.gnat.com (vlsi1.gnat.com
 [IPv6:2620:20:4000:0:250:56ff:fe95:277b])
 by sourceware.org (Postfix) with ESMTP id 546263857C73
 for <gcc@gcc.gnu.org>; Tue, 20 Apr 2021 14:30:23 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 546263857C73
Received: by vlsi1.gnat.com (Postfix, from userid 3004)
 id 2ACFB33CAC; Tue, 20 Apr 2021 10:30:23 -0400 (EDT)
Date: Tue, 20 Apr 2021 10:30:23 EDT
To: david.brown@hesbynett.no
Subject: Re: removing toxic emailers
Cc: gcc@gcc.gnu.org, iant@google.com, jwakely.gcc@gmail.com
In-Reply-To: <beed7493-b7bb-b13c-4fef-974e7cd81a3c@hesbynett.no>
References: <alpine.DEB.2.22.394.2104141745340.94016@digraph.polyomino.org.uk>
 <CAKOQZ8y=tJK2qrANA_e-iEq35hu6wBONFFXUaz6YxEThmOyszw@mail.gmail.com>
 <CAOOE185MDNL.J37YAGWX988I@klugetown>
 <40f0e05b-3156-a649-b636-c90b8b8e0f8@pfeifer.com>
 <4A7DE074-9600-4513-A05C-566926D447BE@tesio.it>
 <535f1dcf-2258-c817-cf72-5c49dc9e5823@hesbynett.no>
 <CAKOQZ8wqh3xY0nH_pAaycdykzwNCCeoVHiZ0UgqPX_RNiMgW3g@mail.gmail.com>
 <20210418131052.GB320802@thyrsus.com>
 <92c014fc39022ea03c6c801bb76ab39674e8a6fb.camel@redhat.com>
 <CAH6eHdTJwiPAweDC5bMaJd5qD5SVe0AnSHKSDFEGZNeVWckU0w@mail.gmail.com>
 <or4kg3pclk.fsf@lxoliva.fsfla.org>
 <CARASROFIMAG.3FXB91YLS7GUV@klugetown>
 <CAH6eHdRcEBWybrAUV3f5FmgZqSm4UrAX==6dKtWPmrJqbyZYAg@mail.gmail.com>
 <542eb0298a485953602e0f28f94b9f03@appliantology.com>
 <CAS8RJUDO44Z.24QC87DO4SOCA@klugetown>
 <CAH6eHdQ2DdWdhGK3M6W+zKuqE86+gQ-vG3=HcPL321yFFSPs6Q@mail.gmail.com>
 <CAKOQZ8zuHu01UG3+3yQr9jnP674GqZ5tUhcAU922wyA8gbJjKw@mail.gmail.com>
 <20210420141528.CD00933CAC@vlsi1.gnat.com>
 <beed7493-b7bb-b13c-4fef-974e7cd81a3c@hesbynett.no>
Message-Id: <20210420143023.2ACFB33CAC@vlsi1.gnat.com>
From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
X-Spam-Status: No, score=-3489.6 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
 KAM_LAZY_DOMAIN_SECURITY, SPF_HELO_NONE, SPF_NONE,
 TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
 server2.sourceware.org
X-BeenThere: gcc@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc mailing list <gcc.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc>,
 <mailto:gcc-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <mailto:gcc-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc>,
 <mailto:gcc-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Apr 2021 14:30:30 -0000

> That would surely only be relevant if people wanted to use their
> telephones to compile code? 

That's not completely clear.  It would certainly be true if the compiler
were included on the phone, whether or not the compiler was actually used.

But I was more addressing the general comment that Google doesn't care
about GPLv3 than the specific issue of GCC.  If the kernel were GPLv3,
for example, there would be an issue with what Samsung is doing.