From: Ian Lance Taylor <iant@google.com>
To: Michael Foley <mjfoley@gmail.com>
Cc: "gcc-help@gcc.gnu.org" <gcc-help@gcc.gnu.org>
Subject: Re: Developing a new feature for gcc
Date: Sun, 29 Dec 2013 23:39:00 -0000 [thread overview]
Message-ID: <CAKOQZ8ycGSOnd7Z5xYvvm=vtr_K1=5n1u4+V-z9eY=PnN3_e+g@mail.gmail.com> (raw)
In-Reply-To: <CAP+Cq-eSu8Jn2CiTp80oe42sooPOfy69HdRZ782bDhGdtiZEaQ@mail.gmail.com>
On Sun, Dec 29, 2013 at 3:31 PM, Michael Foley <mjfoley@gmail.com> wrote:
>
> I have an idea for a feature to be added to the C/C++ compiler, where
> can I find specific information on creating a branch of the code on
> which I can work and also on the legal implications of contributing to
> such an open source project.
On creating a branch: http://gcc.gnu.org/svnwrite.html .
On legal implications: http://gcc.gnu.org/contribute.html .
Ian
prev parent reply other threads:[~2013-12-29 23:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAP+Cq-fXwRvNsOM9iEGmESEdVZokx1kG+uycx+nnz3eEiPZY0A@mail.gmail.com>
2013-12-29 23:31 ` Michael Foley
2013-12-29 23:39 ` Ian Lance Taylor [this message]
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='CAKOQZ8ycGSOnd7Z5xYvvm=vtr_K1=5n1u4+V-z9eY=PnN3_e+g@mail.gmail.com' \
--to=iant@google.com \
--cc=gcc-help@gcc.gnu.org \
--cc=mjfoley@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).