From: <tomas@tuxteam.de>
To: ndame <emacsuser@freemail.hu>
Cc: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: What is the policy for moving a feature into core or not?
Date: Tue, 30 Jul 2019 16:13:06 +0200 [thread overview]
Message-ID: <20190730141306.GD22148@tuxteam.de> (raw)
In-Reply-To: <AxuZA.A41DKD47af5o.TlEsgVVKBiTPrkyqEMO@freemail.hu>
[-- Attachment #1: Type: text/plain, Size: 473 bytes --]
On Tue, Jul 30, 2019 at 04:10:09PM +0200, ndame wrote:
> > My sense is that the OP's question was not so much about
> > mechanics but rather about the level of curation.
>
> Exactly. I don't want to put a package into the core right now. I'm just
> curious if there is a distinction of packages "belonging to the core" or
> anything can go into the core regardless of purpose if the papers are OK.
No idea whether there's any formalism in place.
Cheers
-- t
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2019-07-30 14:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 14:10 What is the policy for moving a feature into core or not? ndame
2019-07-30 14:13 ` tomas [this message]
2019-07-30 14:53 ` Eli Zaretskii
-- strict thread matches above, loose matches on Subject: below --
2019-07-30 11:58 ndame
2019-07-30 13:31 ` tomas
2019-07-30 13:59 ` John Yates
2019-07-30 14:34 ` Stefan Monnier
2019-08-03 17:45 ` Emanuel Berg
2019-08-04 13:05 ` Stefan Monnier
2019-07-30 6:20 ndame
2019-07-30 7:31 ` tomas
2019-12-14 11:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2019-12-14 12:30 ` Óscar Fuentes
2019-12-14 14:05 ` Óscar Fuentes
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=20190730141306.GD22148@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=emacsuser@freemail.hu \
--cc=help-gnu-emacs@gnu.org \
/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.
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).