From: Bastien <bzg@gnu.org>
To: Timothy <tecosaur@gmail.com>
Cc: Matt Huszagh <huszaghmatt@gmail.com>,
emacs-orgmode@gnu.org, Nicolas Goaziou <mail@nicolasgoaziou.fr>
Subject: Re: Supported Emacs version
Date: Mon, 22 Nov 2021 11:26:11 +0100 [thread overview]
Message-ID: <87a6hwcwqk.fsf@gnu.org> (raw)
In-Reply-To: <878rxg7gxm.fsf@gmail.com> (Timothy's message of "Mon, 22 Nov 2021 16:04:06 +0800")
Hi Timothy,
Timothy <tecosaur@gmail.com> writes:
> It’s not the choice I’d make, but what matters more is that I now better
> appreciate/understand the motivation for leaving those bit in.
well, this is always a trade-off: we try to stick to a "users' first*"
principle, while managing the burden for maintainers. If suddenly the
burden of keeping this code is too heavy for maintainers and does not
really benefit the users, we might revise this decision.
> Thanks for discussing this a bit :)
Thanks for bringing this up!
* https://bzg.fr/en/the-software-maintainers-pledge :)
--
Bastien
next prev parent reply other threads:[~2021-11-22 10:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-21 18:41 [PATCH] Fix window width when line numbers present Matt Huszagh
2021-11-21 19:14 ` Timothy
2021-11-21 21:08 ` Nicolas Goaziou
2021-11-21 21:14 ` Matt Huszagh
2021-11-21 21:16 ` Bastien
2021-11-21 21:22 ` Matt Huszagh
2021-11-22 5:14 ` Bastien
2021-11-22 5:31 ` Timothy
2021-11-22 5:44 ` Bastien
2021-11-22 5:51 ` Supported Emacs version (was: [PATCH] Fix window width when line numbers present) Timothy
2021-11-22 6:05 ` Supported Emacs version Bastien
2021-11-22 6:12 ` Timothy
2021-11-22 6:39 ` Bastien
2021-11-22 8:04 ` Timothy
2021-11-22 10:26 ` Bastien [this message]
2021-11-22 11:55 ` [PATCH] Fix window width when line numbers present Ihor Radchenko
2021-11-22 12:40 ` Tim Cross
2021-11-23 5:59 ` Bastien
2021-11-23 7:05 ` Tim Cross
2021-11-22 3:16 ` Timothy
2021-11-21 19:19 ` Timothy
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=87a6hwcwqk.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=huszaghmatt@gmail.com \
--cc=mail@nicolasgoaziou.fr \
--cc=tecosaur@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/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).