From: Paolo Bonzini <paolo.bonzini@gmail.com>
To: Chris Lattner <clattner@apple.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:48:00 -0000 [thread overview]
Message-ID: <4A6742EC.600@gmail.com> (raw)
In-Reply-To: <F2FB45EF-1CA7-4C58-9C86-01E3665BA022@apple.com>
> What is the process for getting a blob of code assigned to the FSF that
> is not just being committed into the tree?
Creating a branch on gcc.gnu.org and committing it there should be enough.
Paolo
next prev parent reply other threads:[~2009-07-22 16:48 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
2009-07-22 16:48 ` Paolo Bonzini [this message]
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=4A6742EC.600@gmail.com \
--to=paolo.bonzini@gmail.com \
--cc=bonzini@gnu.org \
--cc=clattner@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=greg.casamento@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).