Is there a license on patches

[Landon Fuller]

On Nov 9, 2007, at 15:16, Landon Fuller wrote:

>
> On Nov 8, 2007, at 08:58, Emmanuel Hainry wrote:
>
>> Dear list,
>>
>> 		For a port I maintain (namely rubber), there are some patches
>> that upstream has not yet included and are provided by the  
>> maintainer of
>> the port for pkgsrc. They are now in macports repository and I wonder
>> which license if any is applied to patches (as Trac.macports.org  
>> tells
>> people that what they put here is automatically under the Apache  
>> or BSD
>> License). Is there a way to credit the author of a patch and to  
>> cite the
>> license they may be under?
>>
>> 	This problem (but is it a problem?) is, I think, not a rare thing:
>> the work of preparing a program to be part of a ports project is very
>> similar between pkgsrc, openBSD, freeBSD and macports (maybe  
>> gentoo and
>> other linux source based packages too) and hence reusing patches from
>> others is highly probable.
>
> For what it's worth, it's my assumption that any patches I write  
> are licensed
> under the same license as the project.

Er, I should clarify. Licensed under the same license as the project  
*that I'm patching*.

-landonf
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.macosforge.org/pipermail/macports-dev/attachments/20071109/07d402e9/PGP.bin