Cygwin kill utility //Was: cgwin_internal(): difference b/w CW_CYGWIN_PID_TO_WINPID and CW_GETPINFO_FULL for taking only dwProcessId ?

[Tim Prince]

On 4/8/2014 11:21 AM, Christopher Faylor wrote:
> 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.
Now that I'm retired, if I thought there were any point in figuring out 
why gcc test suite fails to kill the hung tests, I'd be happy to send 
any patch.  This comment appears to imply there is no point. Meanwhile, 
I go to Windows task manager and kill them manually, so they report XPASS.
My former employer permitted only employees with a job description 
including support of open source software to submit patches, even though 
we all had to take the annual quiz about GPL etc.  That employer has 
products which run under cygwin bash (not linked against cygwin1.dll), 
some so intended, more of them not.

-- 
Tim Prince


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