From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eggert@cs.ucla.edu, 34849@debbugs.gnu.org, agrambot@gmail.com
Subject: bug#34849: Compilation issues with g++ on some files
Date: Tue, 19 Mar 2019 22:32:33 -0400 [thread overview]
Message-ID: <E1h6R1t-0006Ws-37@fencepost.gnu.org> (raw)
In-Reply-To: <838sxbuxn5.fsf@gnu.org> (message from Eli Zaretskii on Tue, 19 Mar 2019 09:33:02 +0200)
[[[ 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. ]]]
In general, license changes are exactly the sort of thing we need to
prepare fore before the need actually arises.
> I understand the concerns regarding the
> license, but we will need to revisit that when GPL's version is
> advanced, and not sooner.
That reasoning could be valid if we were dealing with computers only.
However, Emacs's users are humans. If they form a habit, they will
oppose changing it.
I don't want there to be humans who insist that Emacs should stay
under GPL v3 so it can continue to be linked with Qt.
This problem could be resolved if Qt moves to GPL 3-or-later.
--
Dr Richard Stallman
President, Free Software Foundation (https://gnu.org, https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2019-03-20 2:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 21:12 bug#34849: Compilation issues with g++ on some files Alex
2019-03-17 5:22 ` Alex
2019-03-18 1:47 ` Richard Stallman
2019-03-18 16:18 ` Alex
2019-03-19 2:24 ` Richard Stallman
2019-03-19 2:37 ` Paul Eggert
2019-03-19 4:45 ` Alex
2019-03-19 7:33 ` Eli Zaretskii
2019-03-20 2:12 ` Paul Eggert
2019-03-20 6:04 ` Alex
2019-03-20 7:05 ` Eli Zaretskii
2019-03-20 6:38 ` Eli Zaretskii
2019-03-20 2:31 ` Richard Stallman
2019-03-20 6:53 ` Eli Zaretskii
2019-03-21 2:09 ` Richard Stallman
2019-03-20 2:32 ` Richard Stallman [this message]
2019-03-20 10:53 ` Dmitry Gutov
2019-03-21 2:10 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1h6R1t-0006Ws-37@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=34849@debbugs.gnu.org \
--cc=agrambot@gmail.com \
--cc=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.