unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Uwe Brauer <oub@mat.ucm.es>
Cc: emacs-devel@gnu.org
Subject: Re: copyright issues and derivative work (the case of matlab-mode)
Date: Tue, 23 Nov 2021 18:44:29 +0200	[thread overview]
Message-ID: <83r1b6om8i.fsf@gnu.org> (raw)
In-Reply-To: <87y25eq1o6.fsf@mat.ucm.es> (message from Uwe Brauer on Tue, 23 Nov 2021 17:25:45 +0100)

> From: Uwe Brauer <oub@mat.ucm.es>
> Date: Tue, 23 Nov 2021 17:25:45 +0100
> 
>     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.
> 
> If b. is the case we are doomed, but I cannot belive that some commit at
> some point acts like a virus «infecting» the descents of that commit,
> till today.

It's a, assuming that those code lines are gone for good, i.e. the
current code is not merely some transformation of those original
lines.  The "annotate" (or "blame") command will not tell you, because
it attributes whole lines; you need to look at the diffs between the
last version that did have that code and the current code, and analyze
that.

Btw, the "15-lines" rule is just an approximation: depending on what
are those lines, it could be much more, or it could be slightly less.
It's a judgment call, not a mechanistic line count.



  reply	other threads:[~2021-11-23 16:44 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 [this message]
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
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=83r1b6om8i.fsf@gnu.org \
    --to=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).