all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Ian Lance Taylor <iant@google.com>
Cc: GCC Development <gcc@gcc.gnu.org>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: clang and FSF's strategy
Date: Tue, 21 Jan 2014 23:02:12 -0500	[thread overview]
Message-ID: <20140122040212.GA4026@thyrsus.com> (raw)
In-Reply-To: <CAKOQZ8yLgvhijZEj0O3CC6Mt4gEJMUF5Bv_EMVnkWCdQPRJ6RA@mail.gmail.com>

Ian Lance Taylor <iant@google.com>:
> I'm sympathetic to our comments regarding GCC vs. clang.  But I'm not
> sure I grasp your proposed solution.  GCC does support plugins, and
> has supported them for a few releases now.

Then I don't understand why David Kastrup's question was even controversial.

If I have failed to understand the background facts, I apologize and welcome
being corrected.

I hope you (and others) understand that I welcome chances to help the FSF's
projects when I believe doing so serves the hacker community as a whole. The
fact that I am currently working full-time on cleaning up the Emacs repoaitory
for full git conversion is only one instance of this.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>


  reply	other threads:[~2014-01-22  4:02 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140122040212.GA4026@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=emacs-devel@gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=iant@google.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.