unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Stefan Kangas <stefankangas@gmail.com>,
	Leo Vivier <zaeph@zaeph.net>, Bastien <bzg@gnu.org>,
	emacs-devel@gnu.org, emacs-orgmode@gnu.org
Subject: Re: bug#66291: [Leo Vivier] [PATCH] orgalist: Update bug:31361 workaround for new upstream signature
Date: Fri, 12 Jan 2024 12:19:43 +0000	[thread overview]
Message-ID: <87o7dqhhgg.fsf@localhost> (raw)
In-Reply-To: <87r0ink9ab.fsf@nicolasgoaziou.fr>

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> 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.

Then, may we need to ask someone to help maintaining orgalist?
Similar question about a number of Org mode libraries where you are
listed as a maintainer.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>



  parent reply	other threads:[~2024-01-12 12:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-09 10:55 [PATCH] orgalist: Update bug:31361 workaround for new upstream signature Leo Vivier
     [not found] ` <CADwFkmkfYQYxOWd953hf+o_Q_ZUDBZV5WnL8FMLiM1PAzgs=Yg@mail.gmail.com>
     [not found]   ` <87edh345dw.fsf@localhost>
     [not found]     ` <CADwFkmnW6_uEbMzCmdjRNOFJ-SNX0DePFTb=hNAnJsqUGWRedg@mail.gmail.com>
     [not found]       ` <87r0ink9ab.fsf@nicolasgoaziou.fr>
2024-01-12 12:19         ` Ihor Radchenko [this message]
2024-02-24 14:00           ` bug#66291: [Leo Vivier] " Bastien Guerry

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=87o7dqhhgg.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=bzg@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    --cc=stefankangas@gmail.com \
    --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).