From: github.com@gnu.support
To: "syl20bnr/spacemacs"
<reply+AF5M4K6ITHAH4ZE2JVWMNLF6JPB5ZEVBNHHDBSUAQA@reply.github.com>
Cc: emacs-tangents@gnu.org
Subject: Re: [syl20bnr/spacemacs] Proposal to improve GPL compliance (#14444)
Date: Wed, 3 Mar 2021 23:02:02 +0300 [thread overview]
Message-ID: <YD/rOojs+4p5oMY9@protected.rcdrun.com> (raw)
In-Reply-To: <syl20bnr/spacemacs/issues/14444/789995307@github.com>
* Tommi Komulainen <notifications@github.com> [2021-03-03 22:26]:
> > Or does @gnusupport think that merely using GNU Emacs to run Spacemacs makes Spacemacs into an Emacs distribution? **Edit:** On further reading https://www.gnu.org/licenses/gpl-faq.html#GPLPlugins, maybe they do. It is very confusing.
Yes, it is new work based on mainstream Emacs. It depends on Emacs and
modifies Emacs in such a way to provide new work.
That is fine and I encourage it and I like it.
Please see the GPL3 where it says:
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.
Spacemacs is based on the earlier work (Emacs). It combines various
parts and various software into one whole.
next prev parent reply other threads:[~2021-03-03 20:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <syl20bnr/spacemacs/issues/14444@github.com>
[not found] ` <syl20bnr/spacemacs/issues/14444/788139959@github.com>
2021-03-01 18:54 ` [syl20bnr/spacemacs] Proposal to improve GPL compliance (#14444) github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/788212009@github.com>
2021-03-03 5:44 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/788214244@github.com>
2021-03-03 6:32 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/788279842@github.com>
2021-03-03 6:59 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/788544413@github.com>
2021-03-03 7:06 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/789479245@github.com>
2021-03-03 7:10 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/788977796@github.com>
2021-03-03 7:17 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/789126947@github.com>
2021-03-03 7:18 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/789468543@github.com>
2021-03-03 7:21 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/789512582@github.com>
2021-03-03 10:08 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/789893593@github.com>
2021-03-03 19:50 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/789995307@github.com>
2021-03-03 20:02 ` github.com [this message]
[not found] ` <syl20bnr/spacemacs/issues/14444/790262904@github.com>
2021-03-04 6:26 ` github.com
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=YD/rOojs+4p5oMY9@protected.rcdrun.com \
--to=github.com@gnu.support \
--cc=emacs-tangents@gnu.org \
--cc=reply+AF5M4K6ITHAH4ZE2JVWMNLF6JPB5ZEVBNHHDBSUAQA@reply.github.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.
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).