public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: mike stump <mrs@windriver.com>
To: jbuck@synopsys.COM, jsm28@cam.ac.uk
Cc: gcc@gcc.gnu.org
Subject: Re: Copyright forms for new contributor?
Date: Tue, 16 Oct 2001 17:53:00 -0000	[thread overview]
Message-ID: <200110170052.RAA17106@kankakee.wrs.com> (raw)

> Date: Tue, 16 Oct 2001 21:54:17 +0100 (BST)
> From: "Joseph S. Myers" <jsm28@cam.ac.uk>
> To: Joe Buck <jbuck@synopsys.COM>
> cc: <gcc@gcc.gnu.org>

> How do the assignments to the FSF interact with the presence of
> non-FSF-copyright files in the tree?  For example, some of the files in
> the gcc/ada directory are copyright FSF, some are copyright Ada Core
> Technologies, some are copyright Florida State University.  If people with
> FSF assignments contribute to these files, do their contributions become
> copyright FSF (rather than any other copyright holder of the files)?

I was surprised to see that the Ada files weren't copyright FSF.
Normally during the import of new code, the code is donated to the
FSF, and the copyright is changed to reflect this fact.  It allows the
FSF to bring a copyright suit against folks that violate copyright,
and it establishes a single clear owner for the work.

Was it intentional that the code not be donated, or have folks just
not gotten around to it yet?

             reply	other threads:[~2001-10-16 17:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-16 17:53 mike stump [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-22  4:13 Richard Kenner
2001-10-21 19:35 dewar
2001-10-22  2:09 ` Richard Earnshaw
2001-10-16  8:46 mike stump
     [not found] <20011012115247.B25697@tornado.cygnus.com>
     [not found] ` <20011012174437.B10341@linux11.lxfarm.csc.liv.ac.uk>
     [not found]   ` <20011012125150.C25999@tornado.cygnus.com>
     [not found]     ` <20011012190633.C10341@linux11.lxfarm.csc.liv.ac.uk>
     [not found]       ` <20011012142725.A26727@tornado.cygnus.com>
     [not found]         ` <20011015112854.A8793@linux11.lxfarm.csc.liv.ac.uk>
     [not found]           ` <20011015095852.D22414@tornado.cygnus.com>
     [not found]             ` <20011015162207.A17825@linux11.lxfarm.csc.liv.ac.uk>
     [not found]               ` <20011015114013.A23365@tornado.cygnus.com>
     [not found]                 ` <20011015173305.B17825@linux11.lxfarm.csc.liv.ac.uk>
2001-10-15  9:39                   ` Diego Novillo
2001-10-16  1:38                     ` Gerald Pfeifer
2001-10-16 12:47                       ` Joe Buck
2001-10-16 13:33                         ` Florian Weimer
2001-10-16 13:43                           ` Diego Novillo
2001-10-16 14:03                             ` Joe Buck
2001-10-16 13:54                         ` Joseph S. Myers
2001-10-16 14:08                           ` Joe Buck
2001-10-17 12:21                         ` Gerald Pfeifer
2001-10-17 17:42                           ` Carlo Wood
2001-10-16 15:09                     ` Craig Rodrigues
2001-10-16 19:38                       ` Joe Buck

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200110170052.RAA17106@kankakee.wrs.com \
    --to=mrs@windriver.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jbuck@synopsys.COM \
    --cc=jsm28@cam.ac.uk \
    /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.
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).