git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j6t@kdbg.org>
Cc: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>,
	"Nicolas Pitre" <nico@fluxnic.net>,
	"Carlo Marcelo Arenas Belón via GitGitGadget"
	<gitgitgadget@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH v2] progress: pay attention to (customized) delay time
Date: Mon, 25 Aug 2025 15:52:19 -0700	[thread overview]
Message-ID: <xmqqh5xvnhek.fsf@gitster.g> (raw)
In-Reply-To: <7b848623-ce64-4679-9b5e-9d91d947b269@kdbg.org> (Johannes Sixt's message of "Mon, 25 Aug 2025 21:16:12 +0200")

Johannes Sixt <j6t@kdbg.org> writes:

>  Compared to the first round, this replaces sig_atomic_t by int. I
>  didn't use bool just in case the patch goes on top of a maintenance
>  track that does not have the "bool is allowed" policy.

That's fair.  I happened to have chosen v2.51.0 as the base for v1
during today's integration, but as a fix-up topic, you are correct
to point out that I should apply this on top of maint-2.50 or even
older.

Thanks, will requeue.

  reply	other threads:[~2025-08-25 22:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-23 13:22 [PATCH 0/2] progress: replace setitimer() with alarm() Carlo Marcelo Arenas Belón via GitGitGadget
2025-08-23 13:22 ` [PATCH 1/2] " Carlo Marcelo Arenas Belón via GitGitGadget
2025-08-23 13:22 ` [PATCH 2/2] progress: add a shutting down state to the SIGALRM handler Carlo Marcelo Arenas Belón via GitGitGadget
2025-08-23 16:24 ` [PATCH 0/2] progress: replace setitimer() with alarm() Johannes Sixt
2025-08-23 19:38   ` Carlo Marcelo Arenas Belón
2025-08-23 19:55     ` Johannes Sixt
2025-08-23 21:33   ` Junio C Hamano
2025-08-23 21:47     ` Junio C Hamano
2025-08-23 22:03     ` Johannes Sixt
2025-08-24 15:31       ` [PATCH] progress: pay attention to (customized) delay time Johannes Sixt
2025-08-25 17:00         ` Junio C Hamano
2025-08-25 18:11           ` Carlo Marcelo Arenas Belón
2025-08-25 18:50             ` Junio C Hamano
2025-08-25 19:16               ` [PATCH v2] " Johannes Sixt
2025-08-25 22:52                 ` Junio C Hamano [this message]
2025-08-24 16:11       ` [PATCH 0/2] progress: replace setitimer() with alarm() 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=xmqqh5xvnhek.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=carenas@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=j6t@kdbg.org \
    --cc=nico@fluxnic.net \
    /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).