X-Recipient:	archive-cygwin AT delorie DOT 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:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=q/cX8Dy/yqhnoSFtwEm9qo4DKOU0aUJvavOh+sEFypLxdrX5QXw5M
	7xyR6BmQxCeyyA4oUk/bSE1uE5bCOuYyyOHmgQ9sdNnTir+8MAmuycYjqq3cRZFB
	uOfeJVBpZfo6TfNKdamS00ubfKnHRIzk++cxXAIkD30gFODZ1rrtco=
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:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=eDboLyBkAJx6yVS0GAiKxCUbEpE=; b=ZEXwFB7IzRV6ecX84Z5AqzBHYZ9E
	dCZ4Y9c+knV9Fogr0OHdZOZ9srLwVHTuxVmHfGcGLK1AIcPFakVWFDJSq63x0Twx
	03Jd/f1e3+GZD+ju7dqqRi7lzHswPL1SHph7jmp24XIsrDh258Eaf9+3V6vAKZui
	3YRJ0iKWwQUxBuI=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-6.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	mho-02-ewr.mailhop.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX18l9qDpN0cR327dx2RseyTX
Date:	Tue, 8 Apr 2014 11:21:18 -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:	<20140408152118.GB4595@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>
MIME-Version:	1.0
In-Reply-To:	<5F8AAC04F9616747BC4CC0E803D5907D0C8B85C2@MLBXv04.nih.gov>
User-Agent:	Mutt/1.5.20 (2009-06-14)

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

If only there was some way to use meaning units to explain legal,
business, or ethical limitations ahead of time which would preclude back
and forth mailing list communications.

Non-sarcastic translation: Don't expect us to know about your s**t.  We
have standard expectations for this free software project and the
expectations are do not include keeping a mental map of the rules of
every email domain that sends messages here so that we can avoid asking
for a patch.

I'm with Corinna in wondering how you can use GPLed software at all if
you are so limited.

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

- Raw text -