From: Richard Stallman <rms@gnu.org>
To: "Perry E. Metzger" <perry@piermont.com>
Cc: dancol@dancol.org, emacs-devel@gnu.org
Subject: Re: lldb support
Date: Sat, 12 Nov 2016 17:30:00 -0500 [thread overview]
Message-ID: <E1c5goC-0003tx-9Z@fencepost.gnu.org> (raw)
In-Reply-To: <20161111195432.237605f4@jabberwock.cb.piermont.com> (perry@piermont.com)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
The more a person shares my general goals and views, the more I value
that person's advice and opinions about my specific decisions.
I think you and I don't have the same goals or the same ideas, so it
is no surprise that you disagree with some of my decisions, or don't
understand them. That doesn't mean I'm mistaken. That you think I
contradicted myself doesn't mean that I did so -- it could simply
mean you don't get the point.
I explain my decisions to the list since that is useful to do. Didn't
I already explain, in 2015, why I think it would be a mistake to
collaborate with a plan to replace our copylefted tools with
non-copylefted ones?
--
Dr Richard Stallman
President, Free Software Foundation (gnu.org, fsf.org)
Internet Hall-of-Famer (internethalloffame.org)
Skype: No way! See stallman.org/skype.html.
next prev parent reply other threads:[~2016-11-12 22:30 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 20:05 lldb support Perry E. Metzger
2016-11-07 20:20 ` Stefan Monnier
2016-11-08 3:08 ` Perry E. Metzger
2016-11-08 13:19 ` Stefan Monnier
2016-11-08 19:58 ` John Wiegley
2016-11-09 0:54 ` Richard Stallman
2016-11-09 1:17 ` Daniel Colascione
2016-11-09 3:42 ` Eli Zaretskii
2016-11-10 0:24 ` Richard Stallman
2016-11-10 0:26 ` Daniel Colascione
2016-11-11 1:26 ` Richard Stallman
2016-11-11 4:24 ` Stefan Monnier
2016-11-11 4:46 ` Nikolaus Rath
2016-11-12 0:42 ` Richard Stallman
2016-11-11 9:44 ` Philippe Vaucher
2016-11-11 17:11 ` Stefan Monnier
2016-11-11 17:42 ` Stefan Huchler
2016-11-11 17:47 ` John Wiegley
2016-11-12 0:59 ` Stefan Huchler
2016-11-12 22:30 ` Richard Stallman
2016-11-14 21:58 ` John Wiegley
2016-11-16 4:13 ` Joseph Mingrone
2016-11-16 14:27 ` Stefan Monnier
2016-12-25 20:43 ` Richard Stallman
2016-11-11 19:01 ` Sam Steingold
2016-11-12 1:02 ` Stefan Huchler
2016-11-12 22:25 ` Richard Stallman
2016-11-12 0:54 ` Perry E. Metzger
2016-11-12 22:30 ` Richard Stallman [this message]
2016-11-10 1:51 ` Perry E. Metzger
2016-11-10 1:57 ` Perry E. Metzger
2016-11-10 3:43 ` Eli Zaretskii
2016-11-10 9:33 ` Toon Claes
2016-11-10 15:57 ` Eli Zaretskii
2016-11-10 16:27 ` Toon Claes
2016-11-10 17:19 ` Eli Zaretskii
2016-11-12 7:04 ` Toon Claes
2016-11-12 7:47 ` Eli Zaretskii
2017-01-04 21:35 ` Toon Claes
2016-11-10 13:58 ` Perry E. Metzger
2016-11-10 16:02 ` Eli Zaretskii
2016-11-09 1:37 ` John Wiegley
2016-11-09 3:06 ` Perry E. Metzger
2016-11-10 0:23 ` Richard Stallman
2016-11-10 1:18 ` John Mastro
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=E1c5goC-0003tx-9Z@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
--cc=perry@piermont.com \
/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).