From: Richard Stallman <rms@gnu.org>
To: Matt Armstrong <matt@rfc20.org>
Cc: gsingh2011@gmail.com, emacs-devel@gnu.org
Subject: Re: Fwd: Should package.el support notifying on package security updates?
Date: Sat, 13 Aug 2022 23:23:13 -0400 [thread overview]
Message-ID: <E1oN4DZ-0001IQ-M6@fencepost.gnu.org> (raw)
In-Reply-To: <87y1vus4xy.fsf@rfc20.org> (message from Matt Armstrong on Thu, 11 Aug 2022 17:04:09 -0700)
[[[ 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. ]]]
We do not endorse or point to MEPLA, because it doesn't uphold our
principles of rejecting nonfree software. So we don't get involved in
maintaining MELPA. We have nothing to do with it.
When there is a package that happens to be in MELPA that we want to
recommend to users, we can put it in NonGNU ELPA. There, we can give
it a little emergency maintenance if that seems called for.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2022-08-14 3:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r12qm4q5.fsf@gmail.com>
2022-08-08 1:46 ` Fwd: Should package.el support notifying on package security updates? Gulshan Singh
2022-08-12 0:04 ` Matt Armstrong
2022-08-12 0:29 ` Tim Cross
2022-08-12 13:18 ` Stefan Kangas
2022-08-13 0:44 ` Tim Cross
2022-08-12 21:40 ` Stefan Monnier
2022-08-13 0:58 ` Tim Cross
2022-08-13 4:58 ` tomas
2022-08-13 14:00 ` Stefan Monnier
2022-08-14 3:23 ` Richard Stallman [this message]
2022-08-14 3:29 ` Gulshan Singh
2022-08-16 2:52 ` Richard Stallman
2022-08-25 3:32 ` Richard Stallman
2022-08-25 4:33 ` Tim Cross
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=E1oN4DZ-0001IQ-M6@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=gsingh2011@gmail.com \
--cc=matt@rfc20.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).