From: Eli Zaretskii <eliz@gnu.org>
To: JD Smith <jdtsmith@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Moving packages out of core to ELPA
Date: Sun, 18 Feb 2024 08:28:16 +0200 [thread overview]
Message-ID: <86r0has2v3.fsf@gnu.org> (raw)
In-Reply-To: <D61A1CC0-7206-4436-A678-1272E4A8FDD0@gmail.com> (message from JD Smith on Sat, 17 Feb 2024 16:16:31 -0500)
> From: JD Smith <jdtsmith@gmail.com>
> Date: Sat, 17 Feb 2024 16:16:31 -0500
> Cc: emacs-devel@gnu.org
>
> >> Not necessarily, depending on how one defines obsolete. Just “no longer worth keeping in core”.
> >
> > That's not my interpretation of your description of IDL state.
>
> Then I fear you may have misinterpreted me. Many astronomers and earth scientists do still use it. A few with emacs. Maybe it’s a bit like Perl that way. There’s a lot of legacy code around. So it’s perfectly valuable to keep in ELPA, but IMO the cost/benefit no longer merits inclusion in core.
Why doesn't the cost/benefit merit inclusion in core?
How do you understand the considerations for keeping something in core
in general?
next prev parent reply other threads:[~2024-02-18 6:28 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 14:40 Moving packages out of core to ELPA JD Smith
2024-02-17 15:51 ` Eli Zaretskii
2024-02-17 16:22 ` JD Smith
2024-02-17 16:51 ` Eli Zaretskii
2024-02-17 17:08 ` JD Smith
2024-02-17 17:29 ` Eli Zaretskii
2024-02-17 18:52 ` JD Smith
2024-02-17 19:20 ` Eli Zaretskii
2024-02-17 20:56 ` [External] : " Drew Adams
2024-02-17 21:16 ` JD Smith
2024-02-18 6:28 ` Eli Zaretskii [this message]
2024-02-18 12:57 ` JD Smith
2024-02-18 13:46 ` Po Lu
2024-02-18 14:03 ` JD Smith
2024-02-18 14:08 ` Po Lu
2024-02-18 14:17 ` JD Smith
2024-02-18 14:17 ` Eli Zaretskii
2024-02-18 14:19 ` JD Smith
2024-02-18 14:22 ` Po Lu
2024-02-17 17:42 ` [External] : " Drew Adams
2024-02-17 18:21 ` JD Smith
2024-02-17 18:32 ` Eli Zaretskii
2024-02-17 19:01 ` JD Smith
2024-02-17 20:50 ` Drew Adams
2024-02-18 1:55 ` Po Lu
2024-02-18 2:27 ` JD Smith
2024-02-18 3:47 ` Po Lu
2024-02-18 1:42 ` Po Lu
2024-02-18 2:14 ` JD Smith
2024-02-18 3:39 ` Po Lu
2024-02-18 7:25 ` Po Lu
2024-02-18 12:39 ` JD Smith
2024-02-18 13:08 ` Eli Zaretskii
2024-02-18 13:15 ` Po Lu
2024-02-18 7:14 ` Eli Zaretskii
2024-02-18 12:19 ` Dmitry Gutov
2024-02-18 13:06 ` Eli Zaretskii
2024-02-18 13:27 ` JD Smith
2024-02-18 13:06 ` Po Lu
2024-02-18 13:13 ` Dmitry Gutov
2024-02-18 13:51 ` Po Lu
2024-02-18 14:19 ` Dmitry Gutov
2024-02-18 14:26 ` Po Lu
2024-02-18 14:38 ` Dmitry Gutov
2024-02-19 18:09 ` Stefan Kangas
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=86r0has2v3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jdtsmith@gmail.com \
/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.