From: chad <yandros@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>,
EMACS development team <emacs-devel@gnu.org>
Subject: Re: Adding use-package to ELPA
Date: Sat, 5 Mar 2022 15:27:32 -0500 [thread overview]
Message-ID: <CAO2hHWZZ43e7oKCExOQGLsQeX-HSVw5BC33xGKR_pmSHUh1qgg@mail.gmail.com> (raw)
In-Reply-To: <871qzgyfuo.fsf@posteo.net>
[-- Attachment #1: Type: text/plain, Size: 636 bytes --]
On Sat, Mar 5, 2022 at 3:17 AM Philip Kaludercic <philipk@posteo.net> wrote:
> [...]
> As mentioned, the question is open whether or not the package should be
> added to ELPA or not (I prefer adding it to ELPA, but I am biased).
>
If you prefer adding it to ELPA as opposed to adding it to the core, could
you expand a bit on why you prefer that? It seems remarkably stable, pretty
amenable to external expansion, and apparently has all of the assignments
lined up (I had thought this was still incomplete, personally), so I would
expect it to be a good fit for core. That said, I haven't looked at the
matter closely.
Thanks,
~Chad
[-- Attachment #2: Type: text/html, Size: 1024 bytes --]
next prev parent reply other threads:[~2022-03-05 20:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 11:42 Adding use-package to ELPA Philip Kaludercic
2022-03-05 5:34 ` Richard Stallman
2022-03-05 8:15 ` Philip Kaludercic
2022-03-05 20:27 ` chad [this message]
2022-03-06 10:31 ` Philip Kaludercic
2022-03-06 23:06 ` John Wiegley
2022-03-07 0:02 ` Philip Kaludercic
2022-03-07 0:34 ` John Wiegley
2022-03-07 2:29 ` Stefan Monnier
2022-03-07 9:02 ` Philip Kaludercic
2022-03-07 18:01 ` Stefan Monnier
2022-03-07 18:42 ` John Wiegley
2022-03-07 19:24 ` Philip Kaludercic
2022-03-07 21:03 ` Stefan Monnier
2022-03-07 23:12 ` Philip Kaludercic
2022-03-07 23:40 ` Stefan Monnier
2022-03-08 8:21 ` Philip Kaludercic
2022-03-08 14:22 ` Stefan Monnier
2022-03-06 5:16 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2022-03-03 11:41 Philip Kaludercic
2022-03-03 14:49 ` Stefan Monnier
2022-03-04 5:57 ` John Wiegley
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=CAO2hHWZZ43e7oKCExOQGLsQeX-HSVw5BC33xGKR_pmSHUh1qgg@mail.gmail.com \
--to=yandros@gmail.com \
--cc=emacs-devel@gnu.org \
--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).