DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=dtLQmaA74VHmAC/U6098TDyLZcM1zqXeG9DShv9Ue3/iCQdNJtMxe
	ofyoo1Jp6Hd8tHr8l+8APofwK6ryXJx1cYYIxtLdTZFSSWFORXfBS08ksR50B0fX
	2icwrTB9ZEl+lUl2NIk4ndAUMOHzDwMK8Eu9Tdu5CXRSjpV+aq9Hoc=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Tue, 8 Apr 2014 12:24:06 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Cygwin kill utility //Was: cgwin_internal(): difference b/w CW_CYGWIN_PID_TO_WINPID and CW_GETPINFO_FULL for taking only dwProcessId ?
Message-ID: <20140408162406.GB5812@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <5F8AAC04F9616747BC4CC0E803D5907D0C8AED9C AT MLBXv04 DOT nih DOT gov> <20140408031817 DOT GA1796 AT ednor DOT casa DOT cgf DOT cx> <5F8AAC04F9616747BC4CC0E803D5907D0C8B4372 AT MLBXv04 DOT nih DOT gov> <20140408090129 DOT GC28755 AT calimero DOT vinschen DOT de> <6CF2FC1279D0844C9357664DC5A08BA2464FF5 AT MLBXV06 DOT nih DOT gov> <5F8AAC04F9616747BC4CC0E803D5907D0C8B85C2 AT MLBXv04 DOT nih DOT gov> <20140408154407 DOT GB25569 AT tastycake DOT net> <20140408155026 DOT GF2437 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20140408155026.GF2437@calimero.vinschen.de>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Tue, Apr 08, 2014 at 05:50:26PM +0200, Corinna Vinschen wrote:
>On Apr  8 16:44, Adam Dinwoodie wrote:
>> On Tue, Apr 08, 2014 at 01:34:21PM +0000, Lavrentiev, Anton (NIH/NLM/NCBI) [C] wrote:
>> > > He's a contractor for the US Government.  That makes things complicated and sometimes seemingly nonsensical.
>> > 
>> > Thanks, Barry.
>> > 
>> > A patch (however small) means code, all my code must under the Public Domain Notice (and which can't be GPL'd).  Thus, our legal
>> > office does not allow us contributing any such code, but verbal description of a problem (hence not constituting code per se) is okay.
>> 
>> I'm not sure what *the* Public Domain Notice is, but I don't know of any
>> public domain "licence" or declaration which isn't compatible with the
>> GNU GPL.  The FSF seems to agree:
>> https://www.gnu.org/licenses/license-list.html#PublicDomain
>> 
>> If you provide a patch with a disclaimer that you are putting the patch
>> in the public domain, I would expect Corinna/cgf/Red Hat would be able
>> to incorporate it into the project.  They can then distribute it under
>> the GPL without you needing to do any of the copyright assignment or
>> distributing anything under the GPL yourself.
>
>Right, as long as it falls under the trivial patch rule.  We usually
>draw the line at about 10 lines of changes.

I'm assuming that it isn't just as trivial as "it's public domain" since
the government is involved.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple