From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: oub@mat.ucm.es, emacs-devel@gnu.org
Subject: Re: copyright issues and derivative work (the case of matlab-mode)
Date: Tue, 23 Nov 2021 23:31:43 -0500 [thread overview]
Message-ID: <E1mpjwd-00061g-22@fencepost.gnu.org> (raw)
In-Reply-To: <83r1b6om8i.fsf@gnu.org> (message from Eli Zaretskii on Tue, 23 Nov 2021 18:44:29 +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. ]]]
> > 3. Patches, that contain more than 15 lines, which according to
> > https://www.gnu.org/prep/maintain/html_node/Legally-Significant.html
> > is legally relevant. However the current HEAD (tip) state of the
> > repository contains less than 15 lines or even no line at all.
> > Now there are two possibilities.
> >
> > a. The orginal patch is no longer relevant, and therefore no action is needed.
> > That is what common sense would tell me.
> >
> > b. Although the code is not present now, it was present in some
> > commit in the past, therefore the rest of the commits is
> > derivative work.
It isn't quite that simple and rigid. The question that needs to be
answered is: is a substantial part of the current code more or less a
rewriting of the original patch? If so, then that part is a
derivative of the original patch.
The FSF can can ask a lawyer about the specific case, if that's
necessary.
--
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:[~2021-11-24 4:31 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 16:25 copyright issues and derivative work (the case of matlab-mode) Uwe Brauer
2021-11-23 16:44 ` Eli Zaretskii
2021-11-23 16:59 ` Uwe Brauer
2021-11-23 17:18 ` Eli Zaretskii
2021-11-23 17:45 ` Uwe Brauer
2021-11-23 18:17 ` Eli Zaretskii
2021-11-25 5:31 ` Richard Stallman
2021-11-25 7:59 ` Eli Zaretskii
2021-11-25 8:03 ` Uwe Brauer
2021-11-25 8:05 ` Eli Zaretskii
2021-11-27 4:08 ` Richard Stallman
2021-11-27 6:19 ` Eli Zaretskii
2021-11-28 4:24 ` Richard Stallman
2021-11-28 8:09 ` Eli Zaretskii
2021-11-29 3:02 ` Richard Stallman
2021-11-29 3:32 ` Eli Zaretskii
2021-11-30 4:10 ` Richard Stallman
2021-11-30 16:45 ` Eli Zaretskii
2021-12-01 7:05 ` Richard Stallman
2021-11-25 8:14 ` Po Lu
2021-11-25 8:33 ` Eli Zaretskii
2021-11-25 9:19 ` Uwe Brauer
2021-11-23 19:56 ` Stefan Monnier
2021-11-24 8:06 ` Uwe Brauer
2021-11-23 20:00 ` Stefan Monnier
2021-11-24 8:00 ` Uwe Brauer
2021-11-24 13:30 ` Stefan Monnier
2021-11-24 4:28 ` Richard Stallman
2021-11-24 7:42 ` Uwe Brauer
2021-11-27 3:24 ` Eric Ludlam
2021-11-28 4:20 ` Richard Stallman
2021-11-28 9:16 ` Uwe Brauer
2021-11-23 20:00 ` Tassilo Horn
2021-11-24 4:31 ` Richard Stallman [this message]
2021-11-24 7:40 ` Uwe Brauer
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=E1mpjwd-00061g-22@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=oub@mat.ucm.es \
/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.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).