From: Alexandre Oliva <oliva@gnu.org>
To: esr@thyrsus.com (Eric S. Raymond)
Cc: rms@gnu.org, gcc@gcc.gnu.org, emacs-devel@gnu.org
Subject: Re: clang and FSF's strategy
Date: Tue, 21 Jan 2014 22:50:12 -0200 [thread overview]
Message-ID: <oreh40q1q3.fsf@livre.home> (raw)
In-Reply-To: <20140121201949.21DE1380522@snark.thyrsus.com> (Eric S. Raymond's message of "Tue, 21 Jan 2014 15:19:49 -0500 (EST)")
On Jan 21, 2014, esr@thyrsus.com (Eric S. Raymond) wrote:
> I think it is time to question whether the anti-plugins policy is
> still the best way to accomplish this.
Err... Excuse me, but what anti-plugins policy are you talking about?
The runtime license exception designed to make room for GCC plugins
without endangering its copyleft is almost 5 years old!
Did you feel so aligned with clang's FSF-disparaging propaganda that you
failed to check the facts, or are you being intentionally specious?
That GCC plugin interface is not sufficiently stable for major
uncoordinated developments by third-parties is just as true as that
Linux's module interface is constantly changing, and complaints about
its lack of stability in it are often responded with such phrases as
“contribute your driver and we'll even help you keep it up-to-date”.
If you were to applaud one while voicing objections to the other,
someone might even get the idea you're using double standards ;-)
--
Alexandre Oliva, freedom fighter http://FSFLA.org/~lxoliva/
You must be the change you wish to see in the world. -- Gandhi
Be Free! -- http://FSFLA.org/ FSF Latin America board member
Free Software Evangelist Red Hat Brazil Toolchain Engineer
next prev parent reply other threads:[~2014-01-22 0:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 20:19 clang and FSF's strategy Eric S. Raymond
2014-01-22 0:07 ` David Kastrup
2014-01-25 15:26 ` David Kastrup
2014-01-22 0:50 ` Alexandre Oliva [this message]
2014-01-23 18:21 ` Joseph S. Myers
2014-01-22 1:31 ` Stefan Monnier
2014-01-22 1:31 ` Ian Lance Taylor
2014-01-22 4:02 ` Eric S. Raymond
2014-01-22 11:27 ` David Kastrup
2014-01-22 14:33 ` Jordi Gutiérrez Hermoso
2014-01-23 10:03 ` Michael Witten
2014-01-23 10:52 ` David Kastrup
2014-01-23 17:17 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2014-01-22 4:49 grischka
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=oreh40q1q3.fsf@livre.home \
--to=oliva@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=esr@thyrsus.com \
--cc=gcc@gcc.gnu.org \
--cc=rms@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).