public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Chris Lattner <clattner@apple.com>
To: Paolo Bonzini <paolo.bonzini@gmail.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
	 Paolo Bonzini <bonzini@gnu.org>,
	 Gregory Casamento <greg.casamento@gmail.com>,
	 stevenb.gcc@gmail.com,  gcc@gcc.gnu.org
Subject: Re: Incorporation of Objective-C 2.0 changes into GCC trunk
Date: Wed, 22 Jul 2009 16:26:00 -0000	[thread overview]
Message-ID: <F2FB45EF-1CA7-4C58-9C86-01E3665BA022@apple.com> (raw)
In-Reply-To: <4A66E2C2.5090107@gmail.com>

On Jul 22, 2009, at 2:58 AM, Paolo Bonzini wrote:
> On 07/22/2009 10:57 AM, Richard Guenther wrote:
>> On Tue, Jul 21, 2009 at 11:14 PM, Paolo Bonzini<bonzini@gnu.org>   
>> wrote:
>>> Gregory Casamento wrote:
>>>> As far as I'm aware apple has an assignment for changes to gcc,  
>>>> so it
>>>> should be possible to pull them in.
>>> You're not forced to assign changes that you do not want to assign.
>>
>> I don't understand.  Yes you are forced to assign copyright to the  
>> FSF
>> for changes you contribute to FSF GCC.  You are of course not forced
>> to do this for your own forks of GCC.
>
> Yeah, if Apple didn't send the code to FSF GCC, the fact that Apple  
> has an assignment does not count.  They're not forced to assign  
> changes that they do not want to assign -- as long as they keep the  
> changes local, which they did for Objective C 2.0.  The only way to  
> know, would be to ask someone at Apple.

If someone is seriously interested in merging pieces of the Apple GCC  
tree into the main FSF tree, and if there is a process in place to  
make the assignment happy, I would be happy to try to make it happen.

The major caveats are that the Apple GCC tree isn't in great shape (it  
will take some work to make the objc2 changes "submission quality"  
because they may break the gnu runtime, be overly darwin specific,  
etc), Apple engineers will not be able to help with this work, and it  
may take some time to get the approval to assign copyright of the code.

What is the process for getting a blob of code assigned to the FSF  
that is not just being committed into the tree?

-Chris 

  reply	other threads:[~2009-07-22 16:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-21 19:47 Gregory Casamento
2009-07-21 19:50 ` Paolo Bonzini
     [not found]   ` <0015175933a6e5738a046f3d1925@google.com>
2009-07-21 21:02     ` Gregory Casamento
2009-07-21 21:14       ` Paolo Bonzini
2009-07-22  8:57         ` Richard Guenther
2009-07-22  9:58           ` Paolo Bonzini
2009-07-22 16:26             ` Chris Lattner [this message]
2009-07-22 16:48               ` Paolo Bonzini
2009-07-22 11:06 ` Dave Korn

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=F2FB45EF-1CA7-4C58-9C86-01E3665BA022@apple.com \
    --to=clattner@apple.com \
    --cc=bonzini@gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=greg.casamento@gmail.com \
    --cc=paolo.bonzini@gmail.com \
    --cc=richard.guenther@gmail.com \
    --cc=stevenb.gcc@gmail.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).