From: Richard Stallman <rms@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: theophilusx@gmail.com, emacs-orgmode@gnu.org
Subject: Re: Supporting non-free SQL clients in ob-sql (was: [PATCH] ob-sql: Add support for Athena)
Date: Fri, 27 Jan 2023 23:45:51 -0500 [thread overview]
Message-ID: <E1pLd67-0001ox-Nq@fencepost.gnu.org> (raw)
In-Reply-To: <877cx9wq64.fsf@localhost> (message from Ihor Radchenko on Thu, 26 Jan 2023 10:22:59 +0000)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> Would it then make sense to note the reasons why we support one or
> another non-free software in a separate file like etc/NON-FREE-SUPPORT?
I think it is a good idea to document the reasoning for these
decision. But I think it does not necessarily have to be centralized
in one file for all of Emacs. Another alternative, also natural,
would be to describe these decisions with the code that implements the
support.
> Also, what about Emacs supporting MS DOS and old versions of Windows? Do
> they still qualify as popular software?
There is no need to include version numbers when we judge whether a
program is well known. People are far more likely to think about a
program name than about its various version numbers.
If a program was once well known, but its use is dwindling, it's not
something we have to worry about informing people about. More people
will have heard of it in the past, than will want to switch to it now.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2023-01-28 4:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 10:48 [PATCH] ob-sql: Add support for Athena Daniel Kraus
2023-01-16 11:13 ` Ihor Radchenko
2023-01-16 11:52 ` Daniel Kraus
2023-01-16 20:50 ` Tim Cross
2023-01-17 9:42 ` Daniel Kraus
2023-01-17 10:06 ` Supporting non-free SQL clients in ob-sql (was: [PATCH] ob-sql: Add support for Athena) Ihor Radchenko
2023-01-17 11:38 ` Tim Cross
2023-01-23 4:23 ` Richard Stallman
2023-01-23 6:33 ` Jean Louis
2023-01-25 4:31 ` Richard Stallman
2023-01-25 7:57 ` Tim Cross
2023-01-25 12:35 ` Ihor Radchenko
2023-01-25 14:05 ` Tim Cross
2023-01-25 14:31 ` Ihor Radchenko
2023-01-25 21:11 ` Tim Cross
2023-02-26 2:59 ` Richard Stallman
2023-01-28 4:45 ` Richard Stallman
2023-01-30 14:51 ` Ihor Radchenko
2023-01-28 4:43 ` Richard Stallman
2023-01-25 11:51 ` Jean Louis
2023-01-29 5:15 ` Richard Stallman
2023-01-23 12:45 ` Ihor Radchenko
2023-01-23 20:12 ` Tim Cross
2023-01-26 4:25 ` Richard Stallman
2023-01-26 6:59 ` Supporting non-free SQL clients in ob-sql Loris Bennett
2023-01-26 10:22 ` Supporting non-free SQL clients in ob-sql (was: [PATCH] ob-sql: Add support for Athena) Ihor Radchenko
2023-01-26 11:05 ` Supporting non-free SQL clients in ob-sql Heinz Tuechler
2023-01-26 11:14 ` Ihor Radchenko
2023-01-26 11:47 ` Heinz Tuechler
2023-01-28 4:45 ` Richard Stallman [this message]
2023-01-29 14:21 ` Supporting non-free SQL clients in ob-sql (was: [PATCH] ob-sql: Add support for Athena) Ihor Radchenko
2023-02-04 5:15 ` Richard Stallman
2023-01-26 4:26 ` Richard Stallman
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=E1pLd67-0001ox-Nq@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=theophilusx@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).