From: JD Smith <jdtsmith@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Dmitry Gutov <dmitry@gutov.dev>, Po Lu <luangruo@yahoo.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Moving packages out of core to ELPA
Date: Sun, 18 Feb 2024 08:27:57 -0500 [thread overview]
Message-ID: <CC3E3876-4921-4DBA-B220-7C3B12E77117@gmail.com> (raw)
In-Reply-To: <867cj1sz0g.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1267 bytes --]
> On Feb 18, 2024, at 8:06 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> Date: Sun, 18 Feb 2024 14:19:05 +0200
>> Cc: luangruo@yahoo.com, emacs-devel@gnu.org
>> From: Dmitry Gutov <dmitry@gutov.dev>
>>
>> On 18/02/2024 09:14, Eli Zaretskii wrote:
>>>>>> It deserves support in Emacs. Just not, IMO, in core.
>>>>> Why not? Why does_anything_, to speak nothing of a package already in
>>>>> core, not "deserve" support in core, while deserving support in ELPA?
>>>> Because in ELPA, users must proactively opt-in to the use of the package. For such users — those who have actively sought it out — in stark contrast to the vast majority of Emacs users, the benefits dramatically outweigh the costs.
>>> The costs are minuscule, so it isn't worth considering them in such
>>> cases.
>>
>> Those who say that the costs of maintenance is tiny, seem to have missed
>> the simple statement
>
> They did?
Indeed my repo diverged substantially from the version in core (>10 yrs ago), because the changes made in core were never communicated to me, and I didn't know to check for them, such that by the time I discovered them, the divergence was too great. This all predated ELPA of course.
I think on all sides this was inadvertent.
[-- Attachment #2: Type: text/html, Size: 2925 bytes --]
next prev parent reply other threads:[~2024-02-18 13:27 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
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 [this message]
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=CC3E3876-4921-4DBA-B220-7C3B12E77117@gmail.com \
--to=jdtsmith@gmail.com \
--cc=dmitry@gutov.dev \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.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.