From: Richard Stallman <rms@gnu.org>
To: Daniel Pittman <slippycheeze@google.com>
Cc: rgm@gnu.org, eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: Licensing for source code contained in Emacs manuals
Date: Mon, 19 Nov 2018 19:49:26 -0500 [thread overview]
Message-ID: <E1gOuEI-0008OI-2g@fencepost.gnu.org> (raw)
In-Reply-To: <CAC45yQtrab484Yk0oc2uBa1ddAOZ2he78rGTS6wgCbad4=dXPQ@mail.gmail.com> (message from Daniel Pittman on Mon, 19 Nov 2018 09:18:18 -0500)
[[[ 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. ]]]
> I'm sorry. I thought that the people here were able to give that
> permission. I will not make any changes until I get a formal notice on the
> subject.
I am the one who can give permission. I will decide on the best way
to address this and I'll get back to you. But I can't do it today.
If you don't hear from me in two weeks, please write to me again (off
the list) to remind me.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2018-11-20 0:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 18:24 Licensing for source code contained in Emacs manuals Daniel Pittman
2018-11-12 20:01 ` Paul Eggert
2018-11-12 21:35 ` Daniel Pittman
2018-11-13 18:31 ` Glenn Morris
2018-11-14 23:13 ` Richard Stallman
2018-11-19 14:18 ` Daniel Pittman
2018-11-20 0:49 ` Richard Stallman [this message]
2018-12-24 2:26 ` Richard Stallman
2019-01-07 21:06 ` Daniel Pittman
2019-01-08 1:06 ` Paul Eggert
2019-01-08 18:57 ` Richard Stallman
2019-06-30 5:05 ` FIXME: When the reader is called in the minibuffer Spenser Truex
2019-06-30 13:50 ` Stefan Monnier
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=E1gOuEI-0008OI-2g@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.org \
--cc=slippycheeze@google.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).