From: Thierry Volpiatto <thievol@posteo.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 48416@debbugs.gnu.org, Stefan Kangas <stefan@marxist.se>
Subject: bug#48416: Release new version of ioccur on GNU ELPA
Date: Tue, 21 Sep 2021 05:26:34 +0000 [thread overview]
Message-ID: <87bl4m7al8.fsf@posteo.net> (raw)
In-Reply-To: <jwvsfxy8zeq.fsf-monnier+emacs@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
Hello Stefan and Stefan :),
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> Stefan Kangas [2021-09-19 08:34:12] wrote:
>> Stefan Kangas <stefan@marxist.se> writes:
>>> Severity: wishlist
>>> The last release of ioccur.el was in 2012. To be fair, not much has
>>> changed since, but I would still suggest releasing a new version to
>>> avoid the cl warnings at least.
I have no cl warnings since Stefan have changed cl to cl-lib, only a
warning about a deprecated function.
Note that this is a deprecated package that will receive no more
changes, you can use instead helm-occur bounded with helm package
(faster, support multi matching, separated sources for each buffer etc...).
> `make fetch/ioccur` tells me that it's up-to-date with the upstream
> repository, so if you want a release, I think you should ask Thierry to
> bump up the `Version:` header.
Done, should I git tag as well?
--
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 686 bytes --]
next prev parent reply other threads:[~2021-09-21 5:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 13:03 bug#48416: Release new version of ioccur on GNU ELPA Stefan Kangas
2021-09-19 15:34 ` Stefan Kangas
2021-09-21 1:58 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-21 5:26 ` Thierry Volpiatto [this message]
2021-09-21 12:27 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-09-21 12:36 ` Thierry Volpiatto
2021-09-25 0:37 ` Stefan Kangas
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=87bl4m7al8.fsf@posteo.net \
--to=thievol@posteo.net \
--cc=48416@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stefan@marxist.se \
/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.