git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Wood <phillip.wood123@gmail.com>
To: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>,
	"Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org, j6t@kdbg.org
Subject: Re: What's cooking in git.git (Jul 2025, #02; Mon, 7)
Date: Wed, 9 Jul 2025 15:15:01 +0100	[thread overview]
Message-ID: <299f547b-635d-4a2c-958e-7ef6200ea69c@gmail.com> (raw)
In-Reply-To: <vl7ahhcqgci3xemqhtdugdhar24ewl7mu4wqwxnc3jag5blpoo@l7b24mahadyi>

On 09/07/2025 11:41, Carlo Marcelo Arenas Belón wrote:
> On Mon, Jul 07, 2025 at 05:11:12PM -0800, Junio C Hamano wrote:
>>
>> * cb/daemon-reap-children (2025-06-26) 4 commits
>>   - daemon: explicitly allow EINTR during poll()
>>   - daemon: use sigaction() to install child_handler()
>>   - compat/mingw: allow sigaction(SIGCHLD)
>>   - compat/posix.h: track SA_RESTART fallback
>>
>>   Futz with SIGCHLD handling in "git daemon".
>>
>>   Stalled?
>>   cf. <dba9ae0d-1e43-4345-a7ec-b57a07d45a07@gmail.com>
>>   source: <pull.2002.v3.git.git.1750927988.gitgitgadget@gmail.com>
> 
> I don't think so, but definitely missing reviews (specially for patch 2)
> and slightly controversial.
> 
> I wasn't planning any further changes,

I'd very much like to see a re-roll cf. 
<b1027221-3e17-40d2-b293-4b1625fa095d@gmail.com>

Thanks

Phillip

> and while I have some for the
> "related" patchset which enhances the notifications by using a self pipe
> was holding them (as well as the related feedback) to allow for this to
> mature on its own.
> 
> On the rationale on why this is independently useful, note that we are
> currently relying in at least 2 "unspecified" behaviours:
> 
> 1) using signal() means that it is implementation defined if SA_RESTART
> will be enabled or not for that signal, and
> 2) if SA_RESTART is enabled, it is implementation defined if we might get
> interrupted in poll().
> 
> both are resolved by using sigaction() instead, and it is up to us to
> decide if SA_RESTART is enabled or not (which might make patch 4 obsolete
> if we decide against).
> 
> Carlo
> 
> 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.
> 


  reply	other threads:[~2025-07-09 14:15 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 [this message]
2025-07-09 15:04   ` Johannes Sixt
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=299f547b-635d-4a2c-958e-7ef6200ea69c@gmail.com \
    --to=phillip.wood123@gmail.com \
    --cc=carenas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j6t@kdbg.org \
    --cc=phillip.wood@dunelm.org.uk \
    /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).