From: Stefan Kangas <stefankangas@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>, Eli Zaretskii <eliz@gnu.org>
Cc: jb@jeremybryant.net, justin@burkett.cc, emacs-devel@gnu.org
Subject: Re: URGENT - which-key FSF contributor status
Date: Tue, 18 Jun 2024 15:06:22 -0400 [thread overview]
Message-ID: <CADwFkmkWH5yBJ55P3+Lge4siXhTBUQ3uNPXQtFPFkKdnFzacDQ@mail.gmail.com> (raw)
In-Reply-To: <CADwFkmmqVr_QS0-SEKh_kmj=GxrXEn=RfF6AYrqyS6Z2off14A@mail.gmail.com>
Stefan Kangas <stefankangas@gmail.com> writes:
> Note these two warnings from package-lint when run on which-key.el:
>
> 806:0: error: "evil-state" doesn't start with package's prefix "which-key".
> 2334:10: error: `next-event' was removed in Emacs version 28.1.
Did you have a chance to look into these warnings?
The first one seems cosmetic, but we might want to fix the second one
(assuming that it's a valid warning).
next prev parent reply other threads:[~2024-06-18 19:06 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87le4r98m9.fsf@jeremybryant.net>
[not found] ` <86le4rjv9p.fsf@gnu.org>
[not found] ` <87a5l78kc0.fsf@posteo.net>
[not found] ` <87msp6o9o4.fsf@jeremybryant.net>
2024-06-15 9:05 ` URGENT - which-key FSF contributor status Philip Kaludercic
2024-06-15 12:30 ` Eli Zaretskii
2024-06-15 12:58 ` Philip Kaludercic
2024-06-15 14:36 ` Stefan Kangas
2024-06-18 19:06 ` Stefan Kangas [this message]
2024-06-18 19:23 ` Philip Kaludercic
2024-06-18 19:30 ` Stefan Kangas
2024-06-18 19:41 ` Philip Kaludercic
2024-06-18 19:42 ` Stefan Kangas
2024-06-18 21:41 ` Philip Kaludercic
2024-06-20 14:26 ` Justin Burkett
2024-06-20 18:25 ` Stefan Kangas
2024-06-20 19:22 ` Philip Kaludercic
2024-06-20 21:16 ` Justin Burkett
2024-06-20 21:45 ` Stefan Kangas
2024-06-15 15:19 ` Eli Zaretskii
2024-06-15 17:09 ` Philip Kaludercic
2024-06-15 17:42 ` Justin Burkett
2024-06-15 17:50 ` Eli Zaretskii
2024-06-18 8:49 ` Philip Kaludercic
2024-06-18 17:37 ` Eli Zaretskii
2024-06-16 19:07 ` Jeremy Bryant
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=CADwFkmkWH5yBJ55P3+Lge4siXhTBUQ3uNPXQtFPFkKdnFzacDQ@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jb@jeremybryant.net \
--cc=justin@burkett.cc \
--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).