VIA C3-2 support.

Gerald Pfeifer pfeifer@dbai.tuwien.ac.at
Sun Feb 9 22:30:00 GMT 2003


On Sun, 9 Feb 2003, Jan Hubicka wrote:
>> As before with Jeff, I don't have a copyright assignment on file,
>> but I'm prepared to offer this patch into public domain and let
>> anyone do what they like with it.
> You can't, as your code is infected by GPL.  You really need assignment
> for anything nontrivial (perhaps this patch is trivial)

I'm not a lawyer, but this is most surely not correct.  Of course, Dave
cannot modify GCC and then put that in the public domain, but surely he
can write a patch and put that very patch in the public domain.

In fact, the FSF has a form of it's own, for precisely this purpose;
it is called request-disclaim.changes and I have included it at the
end of this message.

Gerald


Please email the following information to assign@gnu.org, and we will
send you the disclaimer form for your changes.  This form is preferred
when your changes are small, they do not add any nontrivial new
files, and you are finished making them (aside perhaps from small bug
fixes).

If you would like to make further contributions to the same package,
and you would like to avoid the need to sign more papers when you
contribute them, you have another option: to sign a copyright
assignment covering your future changes.  If that is what you want to
do, please tell the maintainer you would prefer to sign an assignment
of past and future changes.


Please use your full legal name (in ASCII characters) as the subject
line of the message.
-----------------------------------------------------------------------
REQUEST: SEND DISCLAIMER FORM

[What is the name of the program or package you're contributing to?]


[Did you copy any files or text written by someone else in these changes?
Even if that material is free software, we need to know about it.]


[Do you have an employer who might have a basis to claim to own
your changes?]


[Please write your email address here.]


[Please write your snail address here.]





[Please list the files involved, or give a brief description of the
changes being disclaimed.]




More information about the Gcc-patches mailing list