From: Eli Zaretskii <eliz@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 39663@debbugs.gnu.org, larsi@gnus.org, viniciusjl.gnu@gmail.com,
monnier@iro.umontreal.ca
Subject: bug#39663: [External] : bug#39663: 27.1; ebnf2ps bugs
Date: Wed, 01 Sep 2021 15:10:46 +0300 [thread overview]
Message-ID: <83mtowqywp.fsf@gnu.org> (raw)
In-Reply-To: <E8EE43B3-E930-4CC8-BA13-16690172B38C@acm.org> (message from Mattias Engdegård on Wed, 1 Sep 2021 10:23:28 +0200)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Wed, 1 Sep 2021 10:23:28 +0200
> Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
> Drew Adams <drew.adams@oracle.com>, Eli Zaretskii <eliz@gnu.org>,
> "39663@debbugs.gnu.org" <39663@debbugs.gnu.org>,
> Vinicius Jose Latorre <viniciusjl.gnu@gmail.com>
>
> > (And in general, I think moving things to ELPA generally only makes
> > sense if it's a package that somebody wants to work on a lot outside of
> > the Emacs release schedule -- not because it's an outdated package.)
>
> Not sure I agree with that principle -- we'd have to be awfully careful with what we allow in Emacs then, because once in, it can never be removed, even if it didn't really belong in the tree in the first place.
No, we can move such packages to lisp/obsolete/, and after some time
there delete them. It happened in the past.
next prev parent reply other threads:[~2021-09-01 12:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 14:11 bug#39663: 27.1; ebnf2ps bugs Mattias Engdegård
2020-02-18 16:35 ` Stefan Monnier
2020-02-20 15:11 ` Mattias Engdegård
2020-02-24 16:31 ` Stefan Monnier
2020-02-24 16:53 ` Mattias Engdegård
2021-08-30 1:15 ` Lars Ingebrigtsen
2021-08-30 11:39 ` Mattias Engdegård
2021-08-31 1:11 ` Lars Ingebrigtsen
2021-08-31 2:21 ` bug#39663: [External] : " Drew Adams
2021-08-31 3:28 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-08-31 9:14 ` Mattias Engdegård
2021-08-31 13:08 ` Eli Zaretskii
2021-08-31 16:13 ` Drew Adams
2021-09-01 7:53 ` Lars Ingebrigtsen
2021-09-01 8:23 ` Mattias Engdegård
2021-09-01 8:38 ` Lars Ingebrigtsen
2021-09-01 12:10 ` Eli Zaretskii [this message]
2021-09-01 12:08 ` Eli Zaretskii
2021-08-31 15:59 ` Drew Adams
2021-08-31 1:17 ` Lars Ingebrigtsen
2021-08-30 12:53 ` Eli Zaretskii
2021-08-31 1:19 ` Lars Ingebrigtsen
2021-08-31 12:33 ` Eli Zaretskii
2021-09-01 8:05 ` Lars Ingebrigtsen
2021-09-01 12:09 ` Eli Zaretskii
2021-09-02 7:20 ` Lars Ingebrigtsen
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=83mtowqywp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39663@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=mattiase@acm.org \
--cc=monnier@iro.umontreal.ca \
--cc=viniciusjl.gnu@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 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).