This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: SGI releases IA64 C C++ and F90 compiler under GPL
- To: espie at quatramaran dot ens dot fr, toon at moene dot indiv dot nluug dot nl
- Subject: Re: SGI releases IA64 C C++ and F90 compiler under GPL
- From: Mike Stump <mrs at windriver dot com>
- Date: Mon, 22 May 2000 10:54:53 -0700 (PDT)
- Cc: egcs at egcs dot cygnus dot com
> Date: Sun, 21 May 2000 23:00:45 +0200
> From: Marc Espie <espie@quatramaran.ens.fr>
> To: toon@moene.indiv.nluug.nl
> Personally, I would prefer a simpler world, where the FSF would not
> demand copyright ownership. I have some code (leaner, meaner faster
> hash-table) which could benefit gcc, which I am quite willing to
> release under the GPL, but which is also under a BSD license. In
> short, I can't give it to the FSF.
You must not understand something. This is just plain wrong. If you
are the owner, you can do this, 100% of the time, without problem.
The only issue is that bug fixes to the GPLed code cannot necessarily
be used on the other code, and that bug fixes on the other code, would
still need FSF copyright assignment.
The only thing that could prevent you fom giving code to the FSF are
two things, either you must not own it, or you must not want to do it.
> I'm reasonably certain I'm not alone.
If you own the code, I am.
> This problem might even explain why some Net/Free/Open BSD code
> never finds its way into the FSF repository, even though we don't
> really want to maintain the code on our own.
Laziness, not understanding the procedures, intimidation (some may
feel that submitting work to gcc is intimidating), confusion, not
enough perceived benefit verses the cost, not trusting the FSF, not
understanding the GPL... the list goes on.