From: Richard Stallman <rms@gnu.org>
To: emacs-devel@gnu.org
Subject: How often do we have new packages in Whichever ELPA?
Date: Sun, 13 Feb 2022 23:14:40 -0500 [thread overview]
Message-ID: <E1nJSl6-0001Qo-Tv@fencepost.gnu.org> (raw)
In-Reply-To: <jwv8rug1z47.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 11 Feb 2022 23:36:06 -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. ]]]
Can someone please make a list of the last 10 packages added to
GNU ELPA, and the dates of adding them, and likewise for NonGNU ELPA?
If we're concerned about how to avoid disturbing people with too
many messages, let's find out how many they would be.
--
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-02-14 4:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 3:57 Misleading messages about new versions Richard Stallman
2022-02-12 4:36 ` Stefan Monnier
2022-02-14 4:14 ` Richard Stallman [this message]
2022-02-14 8:33 ` How often do we have new packages in Whichever ELPA? Philip Kaludercic
2022-02-15 4:30 ` Richard Stallman
2022-02-15 13:27 ` Eli Zaretskii
2022-02-16 4:14 ` Richard Stallman
2022-02-16 12:18 ` Eli Zaretskii
2022-02-16 10:42 ` Rudolf Schlatte
2022-02-19 4:54 ` Richard Stallman
2022-02-16 18:28 ` Tomas Hlavaty
2022-02-16 20:07 ` Philip Kaludercic
2022-02-19 4:56 ` Richard Stallman
2022-02-17 23:14 ` Richard Stallman
2022-02-14 4:14 ` Misleading messages about new versions Richard Stallman
2022-02-14 12:47 ` Stefan Monnier
2022-02-14 17:27 ` Benjamin Riefenstahl
2022-02-14 18:31 ` Corwin Brust
2022-02-14 18:44 ` Benjamin Riefenstahl
2022-02-14 19:11 ` Jean Louis
2022-02-15 4:31 ` Richard Stallman
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=E1nJSl6-0001Qo-Tv@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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.