From: Bastien Guerry <bzg@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Maske <maske1foro@gmail.com>,
Carsten Dominik <carsten.dominik@gmail.com>,
Org-mode <emacs-orgmode@gnu.org>
Subject: Re: Should we move constants.el by Carsten Dominik to Org orphanage?
Date: Mon, 16 Oct 2023 12:11:54 +0200 [thread overview]
Message-ID: <87ttqqswph.fsf@bzg.fr> (raw)
In-Reply-To: <874jir0w5n.fsf@localhost> (Ihor Radchenko's message of "Mon, 16 Oct 2023 09:11:16 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> Bastien Guerry <bzg@gnu.org> writes:
>
>> I see no reason not to use
>> https://github.com/cdominik/constants-for-Emacs as the source for
>> constants.el, the package seems stable (as its name suggests...)
>
> I was mostly concerned that a pull request back from 2020 is still
> open.
AFAICT the PR is about whitespaces in the README, so not a blocker.
> That said, there is indeed no rush and actually no urgent need to do
> anything - it is not like we are getting an large inflow of bug reports
> related to constants.el.
Indeed :)
--
Bastien Guerry
next prev parent reply other threads:[~2023-10-16 10:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-10 12:02 Erratum in "The Org Manual" 9.6 Maske
2023-09-11 8:13 ` Ihor Radchenko
2023-09-11 8:18 ` Should we move constants.el by Carsten Dominik to Org orphanage? (was: Erratum in "The Org Manual" 9.6) Ihor Radchenko
2023-10-16 5:46 ` Should we move constants.el by Carsten Dominik to Org orphanage? Bastien Guerry
2023-10-16 9:11 ` Ihor Radchenko
2023-10-16 10:11 ` Bastien Guerry [this message]
2024-08-04 9:05 ` Carsten Dominik
2024-08-04 17:43 ` Ihor Radchenko
2024-08-04 18:41 ` Carsten Dominik
2024-08-04 18:51 ` Ihor Radchenko
2024-08-04 20:24 ` Colin Baxter
2024-08-07 4:56 ` Carsten Dominik
2024-08-08 7:45 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ttqqswph.fsf@bzg.fr \
--to=bzg@gnu.org \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=maske1foro@gmail.com \
--cc=yantar92@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/org-mode.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).