From: Philip Kaludercic <philipk@posteo.net>
To: Justin Burkett <justin@burkett.cc>
Cc: Stefan Kangas <stefankangas@gmail.com>,
Eli Zaretskii <eliz@gnu.org>,
jb@jeremybryant.net, emacs-devel@gnu.org
Subject: Re: URGENT - which-key FSF contributor status
Date: Fri, 19 Jul 2024 08:42:24 +0000 [thread overview]
Message-ID: <87v811rcwf.fsf@posteo.net> (raw)
In-Reply-To: <CAF8XuLhV3zdEdfmixQgZifGhKKc91Y0ikXqZHCThhZopUL0T2A@mail.gmail.com> (Justin Burkett's message of "Thu, 18 Jul 2024 07:54:09 -0400")
Justin Burkett <justin@burkett.cc> writes:
> On Wed, Jul 17, 2024 at 6:17 PM Philip Kaludercic <philipk@posteo.net> wrote:
>>
>> Stefan Kangas <stefankangas@gmail.com> writes:
>>
>> > Justin Burkett <justin@burkett.cc> writes:
>> >
>> >> Thank you. Yes, that's very helpful. I prefer the latter option, too.
>> >> I don't foresee many significant changes to which-key, and would
>> >> rather have the process be as simple as possible. I will write up a
>> >> notice in the readme on github and archive the project. There are one
>> >> or two pending contributions, but I can send them through the emacs
>> >> channels to learn about the process if that's alright.
>> >
>> > That sounds good, thank you.
>>
>> One point I just noticed, we haven't bumped the version tag. I just
>> updated elpa.git to follow the core package, but it won't work for now
>> until we release a new version. Are there any specific preferences as
>> to how to proceed here? I would have just changed 3.6.0 to 3.6.1.
>>
>
> That seems fine to me.
OK, I'll update this on the master branch.
> Justin
>
>> --
>> Philip Kaludercic on peregrine
>
>
--
Philip Kaludercic on peregrine
next prev parent reply other threads:[~2024-07-19 8:42 UTC|newest]
Thread overview: 25+ 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
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-07-17 22:17 ` Philip Kaludercic
2024-07-18 11:54 ` Justin Burkett
2024-07-19 8:42 ` Philip Kaludercic [this message]
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=87v811rcwf.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jb@jeremybryant.net \
--cc=justin@burkett.cc \
--cc=stefankangas@gmail.com \
/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).