unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Incorporating patches into GNU Emacs
Date: Sat, 19 Apr 2003 00:14:49 -0400	[thread overview]
Message-ID: <E196jkX-0005fv-00@fencepost.gnu.org> (raw)
In-Reply-To: <microsoft-free.87smsgw6pr.fsf@eicq.dnsalias.org> (message from Steve Youngs on Fri, 18 Apr 2003 18:27:44 +1000)

    The author of the original code needs to assign the copyright to the
    FSF.  For various reasons, the FSF _must_ hold the copyright on every
    single line of code it distributes.  You can't assign a copyright that
    you have no legal right to.  Only the guy with the cool patch, or
    possibly his employer can do that.  And just because you incorporate
    his code into your own doesn't alter the fact that you don't hold the
    copyright to that code.

That is correct.  Only the person who wrote the code can
assign or disclaim the copyright on it.

    The FSF, at its discretion, can waive the requirement of an
    assignment.  What the FSF takes into account when making such a
    decision, I couldn't say.

Our lawyer says we should do this rarely, only when it is very
important.  And we want to get some other sort of contract with
the author in lieu of the normal assignment.

  reply	other threads:[~2003-04-19  4:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-18  6:40 Incorporating patches into GNU Emacs Bill Wohler
2003-04-18  8:27 ` Steve Youngs
2003-04-19  4:14   ` Richard Stallman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-19  3:14 Bill Wohler
2003-04-19 13:35 ` Richard Stallman
2003-04-18 16:11 Bill Wohler
2003-04-18 17:42 ` Stefan Monnier
2003-04-19  0:47   ` Kim F. Storm
2003-04-18  3:31 Bill Wohler
2003-04-18  5:29 ` Steve Youngs

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=E196jkX-0005fv-00@fencepost.gnu.org \
    --to=rms@gnu.org \
    --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).