This is the mail archive of the
mailing list for the GCC project.
Re: Exploring the option to submit the CR16 compiler sourcecode to GNU
- To: geoffk at geoffk dot org
- Subject: Re: Exploring the option to submit the CR16 compiler sourcecode to GNU
- From: DJ Delorie <dj at redhat dot com>
- Date: Tue, 1 May 2001 17:07:26 -0400
- CC: Gali dot Carmel at nsc dot com, gcc at gcc dot gnu dot org
- References: <OFB047CFE2.6445EFC3-ONC2256A3F.0030A522@nsc.com> <firstname.lastname@example.org>
> 1. The new port should be prepared as a patch to the current CVS source
> 2. You need to submit the patch (in the proper format) to the GCC patches
> 3. You need to assign the copyright to the FSF. If the port is currently
I would argue that 3 needs to be done first. If we (the gcc
developers) see your patch before it's assigned, and the assignment
falls through, it will be difficult for us to legally ever port gcc to
the same chip in the future, because we'd be tainted.
You should certainly *start* 3 first, as it often takes the most time.