From: "João Távora" <joaotavora@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel <emacs-devel@gnu.org>, Richard Stallman <rms@gnu.org>,
Jimmy Aguilar Mena <jimmy.aguilar@bsc.es>
Subject: Re: [ELPA] Package cleanup
Date: Wed, 30 Mar 2022 08:56:15 +0100 [thread overview]
Message-ID: <CALDnm53hSoP1eQMSTBXnqkPR2RGxj1ikrPe4n8e4q=MyFys+XA@mail.gmail.com> (raw)
In-Reply-To: <87k0ccxfxy.fsf@yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 786 bytes --]
On Wed, Mar 30, 2022, 04:44 Po Lu <luangruo@yahoo.com> wrote:
> Richard Stallman <rms@gnu.org> writes:
>
> > That suggests they might have bugs and need maintenance, but it does
> > not imply they are useless or obsolete. They might be obsolete, or
> > not.
>
> Indeed. There are some very useful packages that aren't maintained
> anymore (i.e. yasnippet, which hasn't seen changes since 2 years, and
> has no sign of that changing any time soon.)
>
Speaking of which, I'm looking for a maintainer for yasnippet. Noam did an
amazing job for many years, but has moved on. If anyone is interested, let
me know.
A first task would be too sort through the rubble of many unopened issues
and see which ones contain valuable/fixable bugs or suggestions.
João
>
[-- Attachment #2: Type: text/html, Size: 1673 bytes --]
next prev parent reply other threads:[~2022-03-30 7:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 0:43 [ELPA] Package cleanup Jimmy Aguilar Mena
2022-03-29 16:24 ` [External] : " Drew Adams
2022-03-29 21:41 ` John Yates
2022-03-29 22:04 ` Drew Adams
2022-03-29 23:05 ` John Yates
2022-03-30 1:43 ` Drew Adams
2022-03-31 4:27 ` Richard Stallman
2022-03-30 7:31 ` Michael Albinus
2022-03-30 8:35 ` [External] : " Stefan Monnier
2022-03-30 14:09 ` Jimmy Aguilar Mena
2022-03-30 21:23 ` Stefan Monnier
2022-03-31 4:27 ` Richard Stallman
2022-03-30 3:12 ` Richard Stallman
2022-03-30 3:44 ` Po Lu
2022-03-30 7:56 ` João Távora [this message]
2022-03-30 4:56 ` Jimmy Aguilar Mena
2022-04-01 4:07 ` Richard Stallman
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='CALDnm53hSoP1eQMSTBXnqkPR2RGxj1ikrPe4n8e4q=MyFys+XA@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jimmy.aguilar@bsc.es \
--cc=luangruo@yahoo.com \
--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 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).