all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Rudolf Schlatte <rudi@constantly.at>
To: emacs-devel@gnu.org
Subject: Re: How often do we have new packages in Whichever ELPA?
Date: Wed, 16 Feb 2022 11:42:41 +0100	[thread overview]
Message-ID: <m1bkz75bz2.fsf@eduroam-193-157-242-128.wlan.uio.no> (raw)
In-Reply-To: E1nJpTt-0000JC-Ck@fencepost.gnu.org

Richard Stallman <rms@gnu.org> writes:

> So, where is a good place to announce new packages in GNU ELPA?
> Any suggestions?

I think the best place is within Emacs itself, and it is implemented.
When I run `list-packages', all new packages are listed at the beginning
of the resulting buffer, clearly marked as `new' and with a one-line
description.




  parent reply	other threads:[~2022-02-16 10:42 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   ` How often do we have new packages in Whichever ELPA? Richard Stallman
2022-02-14  8:33     ` 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 [this message]
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=m1bkz75bz2.fsf@eduroam-193-157-242-128.wlan.uio.no \
    --to=rudi@constantly.at \
    --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.