public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Andrew Haley <aph@redhat.com>
Cc: Walter Bright <walter@digitalmars.com>, gcc@gcc.gnu.org
Subject: Re: Merging gdc (Gnu D Compiler) into gcc
Date: Tue, 09 Nov 2010 13:57:00 -0000	[thread overview]
Message-ID: <20101109130844.GD2583@sunsite.ms.mff.cuni.cz> (raw)
In-Reply-To: <4CD91608.6050109@redhat.com>

On Tue, Nov 09, 2010 at 09:36:08AM +0000, Andrew Haley wrote:
> > The D specific part of gdc is already GPL, it's just copyrighted by
> > Digital Mars. I understand the copyright must be reassigned to the FSF.
> > Is it possible to fork the code, and assign copyright of one fork to the
> > FSF and leave the other copyrighted by Digital Mars?
> 
> The FSF generally allows a grant-back: that is, you assign your code
> to the FSF, which immediately grants you an unlimited licence to do
> whatever you want with it.

Just note that if you'll want to merge back from the FSF tree back to your
forked tree any changes made there by others, those changes will already be
copyrighted by the FSF and not Digital Mars.

	Jakub

  reply	other threads:[~2010-11-09 13:09 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08 23:13 Walter Bright
2010-11-09  1:14 ` Joseph S. Myers
2010-11-09  7:22   ` Walter Bright
2010-11-09 13:09     ` Andrew Haley
2010-11-09 13:57       ` Jakub Jelinek [this message]
2010-11-09 16:43         ` Joe Buck
2011-10-04  7:08 Merging gdc (GNU " Iain Buclaw
2011-10-04  8:41 ` Andrew Haley
2011-10-04 18:19   ` Iain Buclaw
2011-10-06 15:15   ` Iain Buclaw
2011-10-04 14:03 ` Ian Lance Taylor
2011-10-04 19:30   ` Iain Buclaw
2011-10-04 19:37     ` Andrew Pinski
2011-10-04 20:13       ` Iain Buclaw
2011-10-04 23:11         ` Ian Lance Taylor
2011-10-04 21:41       ` David Brown
2011-10-04 21:47         ` David Brown
2011-10-04 22:51         ` Andrew Pinski
2011-10-05  9:31           ` David Brown
2011-10-05 10:00             ` David Brown
2011-10-05 12:49             ` Andi Kleen
2011-10-05 14:44               ` David Brown
2011-10-05 14:59                 ` David Brown
2011-10-04 20:41     ` Tom Tromey
2011-10-05  0:59     ` Ian Lance Taylor
2011-10-05  4:14       ` Iain Buclaw
2011-10-11 14:05         ` Dave Korn
2011-10-04 16:50 ` Joseph S. Myers
2011-10-04 19:45   ` Iain Buclaw
2011-10-04 19:56     ` Joseph S. Myers
2011-10-06  8:31 ` Walter Bright
2012-04-11 14:12 ` Iain Buclaw
2012-04-13 23:01   ` Dave Korn
2012-05-10  9:37   ` Iain Buclaw
2012-05-10  9:48     ` Richard Guenther
2012-05-10  9:53       ` Iain Buclaw
2012-05-10 11:51         ` Manuel López-Ibáñez
2012-07-21 20:00 ` Florian Weimer
2012-07-24 20:37   ` Iain Buclaw

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=20101109130844.GD2583@sunsite.ms.mff.cuni.cz \
    --to=jakub@redhat.com \
    --cc=aph@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=walter@digitalmars.com \
    /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).