From: "John Wiegley" <johnw@gnu.org>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: pcre2el
Date: Wed, 06 Feb 2019 23:11:16 -0800 [thread overview]
Message-ID: <m2h8dg9ip7.fsf@newartisans.com> (raw)
In-Reply-To: <E1grbOQ-00020p-92@fencepost.gnu.org> (Richard Stallman's message of "Wed, 06 Feb 2019 23:34:30 -0500")
>>>>> "RS" == Richard Stallman <rms@gnu.org> writes:
RS> As a general question, is it a good idea to keep packages in ELPA which
RS> are not maintained? Perhaps in some cases that is ok and in others that is
RS> not.
If they continue to work without much intervention, I don't see much harm in
it. We don't advertise ELPA as being "curated, maintained packages" do we?
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
next prev parent reply other threads:[~2019-02-07 7:11 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 14:09 [ELPA] New package: xr Mattias Engdegård
2019-02-01 15:25 ` Clément Pit-Claudel
2019-02-01 15:42 ` Eli Zaretskii
2019-02-01 18:39 ` Clément Pit-Claudel
2019-02-01 15:51 ` Mattias Engdegård
2019-02-01 18:41 ` Clément Pit-Claudel
2019-02-02 9:43 ` Mattias Engdegård
2019-02-02 15:15 ` Mattias Engdegård
2019-02-02 18:41 ` Clément Pit-Claudel
2019-02-03 9:37 ` Mattias Engdegård
2019-02-03 20:11 ` Juri Linkov
2019-02-03 21:04 ` Mattias Engdegård
2019-02-03 21:13 ` Clément Pit-Claudel
2019-02-05 16:15 ` Stefan Monnier
2019-02-05 22:37 ` Michael Heerdegen
2019-02-06 0:04 ` Mattias Engdegård
2019-02-05 23:00 ` Michael Heerdegen
2019-02-06 0:11 ` Stefan Monnier
2019-02-06 0:25 ` Noam Postavsky
2019-02-06 0:34 ` Michael Heerdegen
2019-02-06 1:36 ` Stefan Monnier
2019-02-06 12:43 ` Mattias Engdegård
2019-02-07 4:34 ` pcre2el Richard Stallman
2019-02-07 7:11 ` John Wiegley [this message]
2019-02-07 14:54 ` pcre2el Stefan Monnier
2019-02-06 0:02 ` [ELPA] New package: xr Mattias Engdegård
2019-02-06 0:14 ` Stefan Monnier
2019-02-06 7:02 ` Richard Stallman
2019-02-06 15:39 ` Eli Zaretskii
2019-02-07 4:36 ` Richard Stallman
2019-02-07 14:37 ` Eli Zaretskii
2019-02-08 3:21 ` Richard Stallman
2019-02-08 3:50 ` Stefan Monnier
2019-02-08 7:18 ` Eli Zaretskii
2019-02-08 10:06 ` Stephen Berman
2019-02-09 3:37 ` Richard Stallman
2019-02-09 8:03 ` Eli Zaretskii
2019-02-09 3:38 ` Richard Stallman
2019-02-09 8:05 ` Eli Zaretskii
2019-02-10 5:51 ` Richard Stallman
2019-02-10 15:12 ` Eli Zaretskii
2019-02-11 5:38 ` Richard Stallman
2019-02-10 5:51 ` Richard Stallman
2019-02-10 15:14 ` Eli Zaretskii
2019-02-09 3:37 ` Richard Stallman
2019-02-27 15:06 ` Michael Heerdegen
2019-02-27 16:22 ` Mattias Engdegård
2019-02-27 17:09 ` Michael Heerdegen
2019-02-28 14:10 ` Mattias Engdegård
2019-02-28 14:34 ` Clément Pit-Claudel
2019-02-28 23:06 ` Stefan Monnier
2019-03-01 13:39 ` Mattias Engdegård
2019-03-01 13:51 ` Stefan Monnier
2019-03-01 5:29 ` Van L
2019-03-01 13:54 ` Stefan Monnier
2019-03-01 15:25 ` Michael Heerdegen
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=m2h8dg9ip7.fsf@newartisans.com \
--to=johnw@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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.
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.