unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Philip Kaludercic <philipk@posteo.net>, emacs-devel@gnu.org
Subject: Re: [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package
Date: Thu, 6 Jan 2022 04:00:33 -0800	[thread overview]
Message-ID: <CADwFkmnu4vnH+9JAbHcO+aLuNxm1QDKn8qcy5hMxqjgdW=7Rsg@mail.gmail.com> (raw)
In-Reply-To: <87k0fdmbat.fsf@posteo.net>

Philip Kaludercic <philipk@posteo.net> writes:

> Stefan Kangas <stefankangas@gmail.com> writes:
>
>> branch: main
>> commit 74116339a852129b98ff79e2eb3aa35b387aa006
>> Author: Stefan Kangas <stefan@marxist.se>
>> Commit: Stefan Kangas <stefan@marxist.se>
>>
>>     * elpa-packages (anzu): New package
>
> Hasn't anzu been obsoleted by isearch-lazy-count?

I don't know; I don't use isearch these days.  I remember using anzu
when I did.

I add packages mostly based on our formal rules, not on if I think they
are useful or good.  Some notable exceptions to this are s.el and f.el,
where we have decided that it is strongly undesirable to promote such
short package prefixes.  I have also skipped some other packages that
are clearly obsolete/no longer developed/bad or low effort, etc.

I am currently focusing on highly popular packages, and anzu clearly fit
the bill with over 1 million downloads on MELPA.org.  It also seems like
it is still maintained, with a new maintainer since March 2020, and
commits as late as October 2021.

But feel free to tell me why I'm wrong; I'm not married to it and if you
think we should remove it again, I don't think I will have any
objections.

BTW, maybe this should be raised as a ticket on the anzu bug tracker?



  reply	other threads:[~2022-01-06 12:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <164145738158.2838.5769558384331859964@vcs2.savannah.gnu.org>
     [not found] ` <20220106082302.0A19CC0DA1E@vcs2.savannah.gnu.org>
2022-01-06 10:02   ` [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package Philip Kaludercic
2022-01-06 12:00     ` Stefan Kangas [this message]
2022-01-06 13:35       ` Philip Kaludercic
2022-01-06 14:30         ` Packages quality (was: [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package) Stefan Monnier
2022-01-06 15:03           ` Bozhidar Batsov
2022-01-06 17:07             ` Packages quality Stefan Monnier
2022-01-06 19:50               ` Tim Cross
2022-01-07  7:54               ` Stefan Kangas
2022-01-07 11:45                 ` John Yates
2022-01-07 12:16                   ` Stefan Kangas
2022-01-07 15:52                     ` John Yates
2022-01-07  7:55             ` Packages quality (was: [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package) Stefan Kangas
2022-01-07 10:22               ` Bozhidar Batsov
2022-01-07 10:54                 ` Stefan Kangas
2022-01-06 17:28           ` Packages quality Philip Kaludercic
2022-01-06 19:55         ` [nongnu] main 74116339a8 2/3: * elpa-packages (anzu): New package Juri Linkov
2022-01-07  7:55         ` Stefan Kangas
2022-01-16 17:49           ` Philip Kaludercic
2022-01-16 22:19             ` Stefan Monnier
2022-01-19  8:57               ` Philip Kaludercic
2022-01-19 15:19                 ` Stefan Monnier
2022-01-16 22:32             ` Stefan Kangas
2022-01-16 23:16               ` Ergus
2022-01-19  9:05                 ` Philip Kaludercic
2022-01-16 23:47               ` Stefan Monnier
2022-01-19  9:03               ` Philip Kaludercic
2022-01-17  7:37             ` Jean Louis
2022-01-19  9:10               ` Philip Kaludercic
2022-01-07 10:02         ` Stefan Kangas
2022-01-10  1:18           ` Stefan Monnier
2022-01-07  9:38     ` Augusto Stoffel

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='CADwFkmnu4vnH+9JAbHcO+aLuNxm1QDKn8qcy5hMxqjgdW=7Rsg@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=emacs-devel@gnu.org \
    --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).