public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Iain Buclaw <ibuclaw@ubuntu.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Merging gdc (GNU D Compiler) into gcc
Date: Tue, 04 Oct 2011 19:45:00 -0000	[thread overview]
Message-ID: <CABOHX+c_M+0qXM=dV=KfW2v3j005b-m_UBJ0XbdvZhi-C50GQA@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1110041632350.10233@digraph.polyomino.org.uk>

On 4 October 2011 17:50, Joseph S. Myers <joseph@codesourcery.com> wrote:
> On Tue, 4 Oct 2011, Iain Buclaw wrote:
>
>> Hi,
>>
>> I've have received news from Walter Bright that the license of the D
>> frontend has been assigned to the FSF. As the current maintainer of
>> GDC, I would like to get this moved forward, starting with getting the
>> ball rolling. What would need to be done? And what are the processes
>> required? (ie: passing the project through to technical review.)
>
> Thanks for working on this.  I think Ian covered the main technical
> points.
>
> Was Digital Mars the only copyright holder?  I see the assignment for
>
> GCC     Digital Mars    2011-10-3
> Assigns Past and Future Changes to the GNU D Compiler
>
> in copyright.list - if any parts (at least any GCC-specific parts in the
> front end as opposed to runtime libraries) have other copyright holders,
> they will also need to have assignments (and any significant changes to
> GCC outside the front end will similarly need to be covered by
> assignments).
>

The original copyrights for the GDC D front-end for GCC are in the
name of David Friedman, who has been MIA since 2007.  Since the
project has been revived, all changes and additions have been
copyrighted in my name, Michael's, and Vincenzo's.  Would I require
approval of these people to assign ownership over to FSF?

Regards
-- 
Iain Buclaw

*(p < e ? p++ : p) = (c & 0x0f) + '0';

  reply	other threads:[~2011-10-04 19:45 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-04  7:08 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2010-11-08 23:13 Merging gdc (Gnu " 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
2010-11-09 16:43         ` 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='CABOHX+c_M+0qXM=dV=KfW2v3j005b-m_UBJ0XbdvZhi-C50GQA@mail.gmail.com' \
    --to=ibuclaw@ubuntu.com \
    --cc=gcc@gcc.gnu.org \
    --cc=joseph@codesourcery.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).