From: Nicolas Goaziou via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Leo Vivier <zaeph@zaeph.net>,
66291-done@debbugs.gnu.org, Ihor Radchenko <yantar92@posteo.net>
Subject: bug#66291: [Leo Vivier] [PATCH] orgalist: Update bug:31361 workaround for new upstream signature
Date: Thu, 11 Jan 2024 19:35:40 +0100 [thread overview]
Message-ID: <87r0ink9ab.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CADwFkmnW6_uEbMzCmdjRNOFJ-SNX0DePFTb=hNAnJsqUGWRedg@mail.gmail.com> (Stefan Kangas's message of "Wed, 10 Jan 2024 10:10:48 -0800")
Hello,
Stefan Kangas <stefankangas@gmail.com> writes:
> Ihor Radchenko <yantar92@posteo.net> writes:
>
>> Stefan Kangas <stefankangas@gmail.com> writes:
>>
>>> The below patches were sent to emacs-devel, but got no followups. I'm
>>> forwarding it here so that we don't lose track of it.
>>>
>>> Please in the future always direct patches to bug-gnu-emacs@gnu.org.
>>
>> It has been a while since we (on Org mailing list) heard from Nicolas.
>> Although, he appears to be active on Guix lists.
>>
>> Nicolas, may I know if you need any help maintaining Org-related packages?
>
> Ping.
I applied the patches and released a new version of Orgalist. Thanks,
and sorry for the delay (!).
To answer Ihor's question : I'm out of touch concerning Org development,
so maintaining a package such as Orgalist may be problematic at some
point, indeed.
I'm closing this report.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2024-01-11 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877cvqmbxh.fsf@hidden>
2023-10-01 12:31 ` bug#66291: [Leo Vivier] [PATCH] orgalist: Update bug:31361 workaround for new upstream signature Stefan Kangas
2023-11-06 9:07 ` Ihor Radchenko
2024-01-10 18:10 ` Stefan Kangas
2024-01-11 18:35 ` Nicolas Goaziou via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=87r0ink9ab.fsf@nicolasgoaziou.fr \
--to=bug-gnu-emacs@gnu.org \
--cc=66291-done@debbugs.gnu.org \
--cc=mail@nicolasgoaziou.fr \
--cc=stefankangas@gmail.com \
--cc=yantar92@posteo.net \
--cc=zaeph@zaeph.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).