Re: [PATCH] t0005: skip signal death exit code test on Windows

From: Johannes Sixt <j.sixt@viscovery.net>
Date: Jun 10, 2013, 05:30 UTC
Message-ID: <51B5648B.7020703@viscovery.net>
In-Reply-To: <7vk3m3owk2.fsf@alter.siamese.dyndns.org>

Am 6/9/2013 22:31, schrieb Junio C Hamano:

Show 10 quoted lines

> Jeff King <peff@peff.net> writes:
> 
>> I'm a little negative on handling just SIGTERM. That would make the test
>> pass, but does it really address the overall issue? To me, the
>> usefulness is having exit values with consistent meanings.
> 
> Yes.  Unless the goal is to give Windows port pratically the same
> signal semantics as ports on other platforms, I do not think special
> casing SIGTERM (unless it is a very common signal on Windows and
> others are unlikely to be useful) buys us much.

I'm thinking the same. And, no, SIGTERM is not very common on Windows.

-- Hannes

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.