This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Cygwin kill utility //Was: cgwin_internal(): difference b/w CW_CYGWIN_PID_TO_WINPID and CW_GETPINFO_FULL for taking only dwProcessId ?
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Tue, 8 Apr 2014 11:21:18 -0400
- Subject: Re: Cygwin kill utility //Was: cgwin_internal(): difference b/w CW_CYGWIN_PID_TO_WINPID and CW_GETPINFO_FULL for taking only dwProcessId ?
- Authentication-results: sourceware.org; auth=none
- 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>
- Reply-to: cygwin at cygwin dot com
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