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: Thu, 10 Jul 2025 09:18:04 +0200 [thread overview]
Message-ID: <51208670-eccc-493f-8a60-2bc9e3a70801@kdbg.org> (raw)
In-Reply-To: <tuglsm3r64mkgzdh2zdrewpzydz7xmyatqxwbbzpqmltwseefc@65cbcs3pq2qg>
Am 10.07.25 um 06:25 schrieb Carlo Marcelo Arenas Belón:
> In d28250654f (Windows: Fix signal numbers, 2009-01-22), the value for
> SIGCHLD was changed from 0 to 17 mentioning some sort of POSIX system.
>
> the relevance comes that if I build a program in Windows that calls
> `signal(SIGCHLD)` using that number I get an error back, but nothing
> on errno, but if the number would be instead 20, like in Cygwin/macOS
> suddenly the behaviour changes and we get the expected EINVAL(20) in errno.
> So do you have any objection on changing the value (which should be otherwise
> unused, and irrelevanted as you pointed out) to 20 then?
I do not object to change the number. Nevertheless, I would like to
understand why it makes a difference. (Currently, I am unable to look
into this myself, though.)
-- Hannes
next prev parent reply other threads:[~2025-07-10 7:18 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
2025-07-10 4:25 ` Carlo Marcelo Arenas Belón
2025-07-10 7:18 ` Johannes Sixt [this message]
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=51208670-eccc-493f-8a60-2bc9e3a70801@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).