From: Johannes Sixt <j6t@kdbg.org>
To: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Cc: git@vger.kernel.org, phillip.wood123@gmail.com,
Junio C Hamano <gitster@pobox.com>
Subject: Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)
Date: Wed, 9 Jul 2025 17:04:51 +0200 [thread overview]
Message-ID: <668ce4d4-3b60-47e0-a4a5-dbf73efd1e75@kdbg.org> (raw)
In-Reply-To: <vl7ahhcqgci3xemqhtdugdhar24ewl7mu4wqwxnc3jag5blpoo@l7b24mahadyi>
Am 09.07.25 um 12:41 schrieb Carlo Marcelo Arenas Belón:
> CC: Johannes Sixt on feedback for SIGCHLD in mingw which uses 17 instead
> of 22 (cygwin and others) and therefore seem to cause signal to err
> without setting errno as it should.
I don't know what the relevance of the actual number of a signal is.
Nobody is supposed to use the number, only the macro. But I may be
misjudging the situation as a bystander of this discussion.
Furthermore, there is no such thing as "a signal" on Windows (outside of
Cygwin), let alone a SIGCHLD. Therefore, this topic about SA_RESTART is
irrelevant for the MinGW port.
That said, we have a very stupid emulation of SIGALRM, but it doesn't
work like a POSIX signal in any way (if it works at all).
-- Hannes
next prev parent reply other threads:[~2025-07-09 15:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-08 0:11 What's cooking in git.git (Jul 2025, #02; Mon, 7) Junio C Hamano
2025-07-08 0:47 ` Ayush Chandekar
2025-07-09 9:25 ` René Scharfe
2025-07-09 15:37 ` Junio C Hamano
2025-07-09 10:41 ` Carlo Marcelo Arenas Belón
2025-07-09 14:15 ` Phillip Wood
2025-07-09 15:04 ` Johannes Sixt [this message]
2025-07-10 4:25 ` Carlo Marcelo Arenas Belón
2025-07-10 7:18 ` Johannes Sixt
2025-07-10 15:30 ` Junio C Hamano
2025-07-09 16:26 ` Junio C Hamano
2025-07-09 14:46 ` Taylor Blau
2025-07-10 0:01 ` Junio C Hamano
2025-07-10 1:05 ` Elijah Newren
2025-07-10 4:24 ` Junio C Hamano
2025-07-09 23:14 ` brian m. carlson
2025-07-10 4:24 ` Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=668ce4d4-3b60-47e0-a4a5-dbf73efd1e75@kdbg.org \
--to=j6t@kdbg.org \
--cc=carenas@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=phillip.wood123@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).