From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: philipk@posteo.net, hi@ypei.me, emacs-devel@gnu.org
Subject: Re: Adding major or popular language modes to Emacs distribution
Date: Sat, 28 Aug 2021 16:37:12 +0300 [thread overview]
Message-ID: <835yvpoflj.fsf@gnu.org> (raw)
In-Reply-To: <jwvilzpn2f5.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sat, 28 Aug 2021 09:14:55 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Philip Kaludercic <philipk@posteo.net>, Emacs Devel mailing list
> <emacs-devel@gnu.org>
> Date: Sat, 28 Aug 2021 09:14:55 -0400
>
> > This makes sense. But does this mean if I want to add new language modes it
> > should go to GNU ELPA rather than Emacs itself?
>
> As a former Emacs maintainer and as de-facto maintainer of (Non)GNU
> ELPA, I think the answer here is "yes", basically.
>
> There are some packages which we want to include in Emacs itself, either
> because they're expected to be used by a large fraction of Emacs users,
> or because they're used by other packages included in Emacs, but for
> most of the rest we prefer to accept new packages into GNU ELPA than
> into Emacs, because it offers more flexibility (e.g. in terms of
> release schedules).
When you say "we prefer" here you mean you personally, right? Because
there's no such project-wide policy, AFAICT, and I at least don't
agree.
next prev parent reply other threads:[~2021-08-28 13:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 23:04 Adding major or popular language modes to Emacs distribution Yuchen Pei
2021-08-27 23:12 ` Philip Kaludercic
2021-08-27 23:31 ` Yuchen Pei
2021-08-28 2:38 ` Arthur Miller
2021-08-28 6:47 ` Eli Zaretskii
2021-08-28 11:34 ` Qiantan Hong
2021-08-28 11:52 ` Eli Zaretskii
2021-08-28 13:14 ` Stefan Monnier
2021-08-28 13:37 ` Eli Zaretskii [this message]
2021-08-28 13:42 ` Dmitry Gutov
2021-08-28 13:49 ` Eli Zaretskii
2021-08-28 14:16 ` Dmitry Gutov
2021-08-28 14:37 ` Eli Zaretskii
2021-08-28 14:46 ` Dmitry Gutov
2021-08-28 15:01 ` Eli Zaretskii
2021-08-28 14:59 ` Lars Ingebrigtsen
2021-08-28 15:03 ` Eli Zaretskii
2021-08-28 6:24 ` Eli Zaretskii
2021-08-28 13:45 ` Philip Kaludercic
2021-08-28 13:56 ` Eli Zaretskii
2021-08-28 14:30 ` Philip Kaludercic
2021-08-28 14:40 ` Eli Zaretskii
2021-08-28 14:45 ` Theodor Thornhill
2021-08-28 14:58 ` Eli Zaretskii
2021-08-28 15:03 ` Arthur Miller
2021-08-28 15:09 ` Eli Zaretskii
2021-08-28 15:32 ` Philip Kaludercic
2021-08-28 15:53 ` Lars Ingebrigtsen
2021-08-28 16:28 ` Theodor Thornhill
2021-08-28 20:40 ` Dmitry Gutov
2021-08-29 2:15 ` Ergus
2021-08-29 6:40 ` Eli Zaretskii
2021-08-28 16:55 ` Arthur Miller
2021-08-28 17:02 ` Theodor Thornhill
2021-08-28 6:21 ` Eli Zaretskii
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=835yvpoflj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=hi@ypei.me \
--cc=monnier@iro.umontreal.ca \
--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).