X-Recipient: archive-cygwin@delorie.com
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:references
	:mime-version:content-type:in-reply-to; q=dns; s=default; b=n4ea
	A5x7Mnpwtc7rM3cnKUqYUIIthMGBw/9rPu+zk0Jt0p2DHRkMX9dX4zGGHZhatLY5
	GfpiY65CHwizifOwpOGDM35pBFPqKo29TiL2gsdq8us67pWeFXspHs5lTbNk1Ugr
	NBV/fBnG1VWRu/Fx9iUN/dQxXQIe35yUPceEwj8=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:references
	:mime-version:content-type:in-reply-to; s=default; bh=6lGMF6S9Ic
	9rPwuCTg593YlORUo=; b=qH1X2TD+hlhEsmqiN0fHwZ+3co7HTXr3jLWyGdo4Om
	E/Lg+T3gcY98iUPcfVmb/B8CcNjTJHQjmE2R/bzEu89XLEEMjEXpUvwNcnuRPf7D
	9mbODODGKGNTPPCY6aSlRyAStedVJWNDOhj3PcAWowdXhSRdZI12vJpDBgvr2HNt
	8=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS autolearn=ham version=3.3.2
X-HELO: northrend.tastycake.net
Date: Tue, 8 Apr 2014 16:44:07 +0100
From: Adam Dinwoodie <adam@dinwoodie.org>
To: cygwin@cygwin.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: <20140408154407.GB25569@tastycake.net>
References: <5F8AAC04F9616747BC4CC0E803D5907D0C8AED9C@MLBXv04.nih.gov> <20140408031817.GA1796@ednor.casa.cgf.cx> <5F8AAC04F9616747BC4CC0E803D5907D0C8B4372@MLBXv04.nih.gov> <20140408090129.GC28755@calimero.vinschen.de> <6CF2FC1279D0844C9357664DC5A08BA2464FF5@MLBXV06.nih.gov> <5F8AAC04F9616747BC4CC0E803D5907D0C8B85C2@MLBXv04.nih.gov>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5F8AAC04F9616747BC4CC0E803D5907D0C8B85C2@MLBXv04.nih.gov>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-IsSubscribed: yes

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.

--
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

