unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: emacs-devel@gnu.org
Subject: Re: copyright issues and derivative work (the case of matlab-mode)
Date: Wed, 24 Nov 2021 09:06:53 +0100	[thread overview]
Message-ID: <87tug2nfj6.fsf@mat.ucm.es> (raw)
In-Reply-To: jwv4k82bqcq.fsf-monnier+emacs@gnu.org

[-- Attachment #1: Type: text/plain, Size: 1233 bytes --]

>>> "SM" == Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> The question is should I «rewrite» the repository changing commits and
>> trying to add the name of the authors before it will, hopefully one day
>> enter ELPA?

> As long as the code is not in `elpa.git`, it's up to you to decide
> whether to perform such rewrites.  Once it's in `elpa.git` such rewrites
> should be avoided at (almost) all cost.

That is what I thought.

> It sounds like a lot of work and could lead to trouble for other people
> who're tracking your repository, so I probably wouldn't do it if I were you.

Right, after some thinking I decided not to start with it, GNU emacs
has also been transformed many times, from RCS(?) To CVS to bazzarr to
git.

Its first commit reads 
,----
| 
| ◍  commit 0:ce5584125c44a1a2fbb46e810459c50b227a95e2
|    Author: Jim Blandy <jimb@redhat.com>
|    Date: Thu, 18 Apr 1985 00:48:29 +0000
| 
|    entered into RCS
`----

Which has we discussed some time ago is impossible since redhat was
Founded: March 26, 1993, Raleigh, North Carolina, United States,
according to wikipedia 😝.

So a repository this old is different from one started freshly with git
or mercurial.

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

  reply	other threads:[~2021-11-24  8:06 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 [this message]
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=87tug2nfj6.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=emacs-devel@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 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).