From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: [PATCHES] 21.3.50 for Cygwin: patch 7
Date: 11 Dec 2002 01:30:41 +0100 [thread overview]
Message-ID: <5xisy1jt1q.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <3DF67390.2020106@hekimian.com>
Joe Buehler <jbuehler@hekimian.com> writes:
> Kim F. Storm wrote:
>
> > We usually cannot copy (or adapt) stuff from XEmacs, as we require
> > papers from the original author, as well as anyone who has contributed
> > with anything but tiny changes to the code.
>
> The files I copied already had copyright notices that say that the FSF
> owns the files. Is that adequate?
We require papers for all "non-tiny" changes that are installed in CVS.
In this case, the file builds on source "owned by FSF", but although
that means that the GPL applies to the changed file, that doesn't make
FSF "owner" of any work derived from that source.
So if the file has been changed "outside" FSF, we require papers!
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2002-12-11 0:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 21:48 [PATCHES] 21.3.50 for Cygwin: patch 7 Joe Buehler
2002-12-11 0:01 ` Kim F. Storm
[not found] ` <3DF67390.2020106@hekimian.com>
2002-12-11 0:30 ` Kim F. Storm [this message]
2002-12-12 14:30 ` Joe Buehler
2002-12-12 16:16 ` Joe Buehler
2002-12-12 17:23 ` Eli Zaretskii
2002-12-13 22:21 ` Richard Stallman
2002-12-12 17:09 ` Kim F. Storm
2002-12-13 22:21 ` Richard Stallman
2002-12-12 18:14 ` Paul Eggert
2002-12-13 15:14 ` Joe Buehler
2002-12-14 18:32 ` Richard Stallman
2002-12-16 14:37 ` Joe Buehler
2002-12-16 15:03 ` Juanma Barranquero
2002-12-16 17:33 ` Joe Buehler
2002-12-18 10:10 ` Juanma Barranquero
2002-12-18 13:46 ` Joe Buehler
2002-12-18 16:45 ` Juanma Barranquero
2002-12-19 18:32 ` Richard Stallman
2002-12-11 19:53 ` Jason Rumney
-- strict thread matches above, loose matches on Subject: below --
2002-12-16 15:58 jasonr
2002-12-16 16:40 ` Juanma Barranquero
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=5xisy1jt1q.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--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).