This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: FSF Policy re. inclusion of source code from other projects in GCC
- From: Joe Buck <Joe dot Buck at synopsys dot COM>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: Benjamin Kosnik <bkoz at redhat dot com>, Loren James Rittle <rittle at latour dot labs dot mot dot com>, gcc at gcc dot gnu dot org
- Date: Fri, 17 Mar 2006 15:10:22 -0800
- Subject: Re: FSF Policy re. inclusion of source code from other projects in GCC
- References: <mailman.3808.1142630022.1706.gnu-gcc-patches@lists.nsr.labs.mot.com> <200603172215.k2HMFhar001685@latour.labs.mot.com> <20060317164920.7f7b77e7.bkoz@redhat.com> <441B40AD.2070505@codesourcery.com>
On Fri, Mar 17, 2006 at 03:05:17PM -0800, Mark Mitchell wrote:
> Benjamin Kosnik wrote:
> >>> The STL files in libstdc++-v3 need to be clearly marked as not part of
> >>> GCC. Benjamin, will you please take care of that, by modifying the
> >>> libstdc++-v3/README to indicate that the files originally from HP are
> >>> not part of GCC, and specifically list those files?
> >
> > Huh? What are you smoking dude?
>
> Nothing; I don't smoke.
>
> As already stated, all I am doing is passing along information from the
> FSF. RMS personally approved the message that I sent, including the
> discussion of the STL files.
>
> As previously stated, if there is contrary information from FSF lawyers,
> then please gather it and present it to the FSF.
Please, no one panic yet. I recall the facts as Ben stated them, but
I can't lay hands on the old emails. I think that we can convince
RMS that the STL usage in libstdc++ isn't a problem, and it's best to
do that offline.