From: Jean Louis <bugs@gnu.support>
To: Tassilo Horn <tsdh@gnu.org>
Cc: Davin Pearson <davin.pearson@gmail.com>, help-gnu-emacs@gnu.org
Subject: Re: Fwd: How do I go about debugging my Elisp code?
Date: Sat, 15 Jan 2022 10:35:44 +0300 [thread overview]
Message-ID: <YeJ5UGKtjwuX7tnO@protected.localdomain> (raw)
In-Reply-To: <87a6fyw0kh.fsf@gnu.org>
* Tassilo Horn <tsdh@gnu.org> [2022-01-14 23:00]:
> > CC BY-SA 4.0 is one-way compatible with the GNU GPL version 3: this
> > means you may license your modified versions of CC BY-SA 4.0 materials
> > under GNU GPL version 3, but you may not relicense GPL 3 licensed
> > works under CC BY-SA 4.0.
>
> Aren't they doing exactly the latter when allowing elisp code to be
> posted?
That question I don't get.
> According to your argument, every elisp code is a modification of
> emacs itself and therefore must have the same license (or at least
> equivalent terms) as emacs.
Yes. My understanding is that CC BY-SA 4.0 license is compatible to
GPL 3+ and thus all contributions on Emacs StackExchange are
compatible to Emacs license, thus fine in that regard.
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2022-01-15 7:35 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAG9ihEv+vex+5=PLcn2Pvs1RLQQgGVjjD7_sGxcZOYscr2mj=g@mail.gmail.com>
2022-01-13 1:22 ` Fwd: How do I go about debugging my Elisp code? Davin Pearson
2022-01-13 1:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-13 12:58 ` Michael Heerdegen
2022-01-14 6:55 ` Marcin Borkowski
2022-01-14 8:24 ` Jean Louis
2022-01-14 23:22 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-14 13:46 ` Jean Louis
2022-01-14 14:56 ` Tassilo Horn
2022-01-14 15:20 ` Jean Louis
2022-01-14 16:23 ` Tassilo Horn
2022-01-14 16:53 ` Jean Louis
2022-01-14 17:24 ` Tassilo Horn
2022-01-14 17:57 ` Jean Louis
2022-01-14 18:58 ` Tassilo Horn
2022-01-15 7:34 ` Jean Louis
2022-01-14 18:56 ` Marcin Borkowski
2022-01-14 19:02 ` Jean Louis
2022-01-14 19:51 ` Tassilo Horn
2022-01-15 7:35 ` Jean Louis [this message]
2022-01-15 10:15 ` Tassilo Horn
2022-01-15 11:33 ` Jean Louis
2022-01-18 0:03 ` Davin Pearson
2022-01-14 23:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-14 23:26 ` NonGNU ELPA (was: Re: Fwd: How do I go about debugging my Elisp code?) Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-15 7:39 ` Jean Louis
2022-01-17 3:47 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-17 18:15 ` Jean Louis
2022-01-18 0:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-18 5:02 ` Jean Louis
2022-01-18 6:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-18 3:02 ` NonGNU ELPA Stefan Monnier via Users list for the GNU Emacs text editor
2022-01-18 3:20 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-18 3:49 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-01-21 21:32 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-22 4:00 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-01-22 4:53 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-22 5:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-22 5:24 ` Po Lu
2022-01-22 5:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-22 6:32 ` Po Lu
2022-01-22 6:42 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-22 7:10 ` Po Lu
2022-01-22 12:24 ` Jean Louis
2022-01-22 12:38 ` Po Lu
2022-01-22 11:13 ` Jean Louis
2022-01-22 13:43 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-23 9:24 ` Jean Louis
2022-01-23 16:26 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-01-23 16:39 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-22 4:58 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-22 5:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-18 3:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-14 17:40 ` Fwd: How do I go about debugging my Elisp code? Yuri Khan
2022-01-14 17:51 ` Jean Louis
2022-01-14 23:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-14 23:24 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-15 2:13 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-15 8:24 ` Jean Louis
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=YeJ5UGKtjwuX7tnO@protected.localdomain \
--to=bugs@gnu.support \
--cc=davin.pearson@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=tsdh@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.
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).