From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: philipk@posteo.net, eshelshay.yaron@gmail.com,
emacs-devel@gnu.org, jan@swi-prolog.org
Subject: Re: [NonGNU ELPA] New package: sweep
Date: Wed, 28 Sep 2022 21:41:44 +0300 [thread overview]
Message-ID: <831qrvibo7.fsf@gnu.org> (raw)
In-Reply-To: <868rm376hl.fsf@mail.linkov.net> (message from Juri Linkov on Wed, 28 Sep 2022 20:49:10 +0300)
> From: Juri Linkov <juri@linkov.net>
> Cc: Eshel Yaron <eshelshay.yaron@gmail.com>, emacs-devel@gnu.org, Jan
> Wielemaker <jan@swi-prolog.org>
> Date: Wed, 28 Sep 2022 20:49:10 +0300
>
> I wonder where this requirement to put all tags in the package name comes from?
Your examples are all from MELPA. Why not take a few examples from
Emacs?
next prev parent reply other threads:[~2022-09-28 18:41 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 11:29 [NonGNU ELPA] New package: sweep Eshel Yaron
2022-09-26 19:32 ` Philip Kaludercic
2022-09-27 16:32 ` Eshel Yaron
2022-09-27 17:46 ` Philip Kaludercic
2022-09-28 6:46 ` Eshel Yaron
2022-09-28 7:27 ` Philip Kaludercic
2022-09-28 17:49 ` Juri Linkov
2022-09-28 18:41 ` Eli Zaretskii [this message]
2022-09-28 18:56 ` Philip Kaludercic
2022-09-30 2:38 ` Richard Stallman
2022-09-30 8:20 ` Stefan Kangas
2022-09-30 9:45 ` Robert Pluim
2022-09-29 2:59 ` Richard Stallman
2022-09-29 16:53 ` [NonGNU ELPA] New package: sweeprolog Eshel Yaron
2022-09-29 16:59 ` Philip Kaludercic
2022-10-01 2:01 ` Richard Stallman
2022-09-27 18:49 ` [NonGNU ELPA] New package: sweep Stefan Monnier
2022-09-28 7:15 ` Eshel Yaron
2022-09-29 3:02 ` Richard Stallman
2022-09-29 5:04 ` Eshel Yaron
2022-09-29 6:17 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2022-09-26 10:22 Eshel Yaron
2022-09-26 17:41 ` Stefan Monnier
2022-09-27 15:19 ` Eshel Yaron
2022-09-30 2:36 ` Richard Stallman
2022-09-27 16:17 ` Richard Stallman
2022-09-27 18:47 ` Juri Linkov
2022-09-28 5:40 ` Andrea G. Monaco
2022-09-30 2:36 ` 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
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=831qrvibo7.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=eshelshay.yaron@gmail.com \
--cc=jan@swi-prolog.org \
--cc=juri@linkov.net \
--cc=philipk@posteo.net \
/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).