git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2025, #01; Mon, 7)
Date: Wed, 9 Apr 2025 07:31:03 -0400	[thread overview]
Message-ID: <d5588a3d-db07-5c4e-3c22-ad4b751dd3fc@gmail.com> (raw)
In-Reply-To: <xmqqmscqyag7.fsf@gitster.g>

Hi Junio and Patrick,

Le 2025-04-08 à 10:50, Junio C Hamano a écrit :
> Patrick Steinhardt <ps@pks.im> writes:
> 
>> On Mon, Apr 07, 2025 at 04:49:28PM +0000, Junio C Hamano wrote:
>>> * pb/perf-test-fixes (2025-03-28) 2 commits
>>>  - p9210: fix 'scalar clone' when running from a detached HEAD
>>>  - p7821: fix test_perf invocation for prereqs
>>>
>>>  "make perf" fixes.
>>>
>>>  Will merge to 'next'?
>>>  cf. <Z-pD1puYT87YKAd4@pks.im>
>>>  source: <pull.1936.git.git.1743181669.gitgitgadget@gmail.com>
>>
>> I had one question around empty prereqs introduced by the patch that
>> wasn't yet answered. Based on my testing empty prereqs do work just fine
>> though and evaluate to true, so the patch series looks fine to me.

Patrick, thank you for your review on this series, and for testing it.
I do intend to answer you in that thread, and I also wanted to actually test
what you mentioned about empty prereqs, I just have very limited time to
contribute these days, so I don't know when I'll be able to.

Junio, I see this was merged to 'next' already yesterday (the 8th), and
you sent this "What's cooking" on the 7th. Would it be possible to wait 
more than one day before announcing an upcoming merge to 'next' of a series
and the actual merge ? This would allow contributors with very little time
to contribute a little more time to say so if they wish to wait 
before merging to next because they want to send a new iteration. 

P.S. I can't answer these mails on my phone because of the plain-text only
requirement on the list (at least, I do not know of an iOS mobile client that
can send plain-text only).

Thank you,

Philippe.

  reply	other threads:[~2025-04-09 11:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 16:49 What's cooking in git.git (Apr 2025, #01; Mon, 7) Junio C Hamano
2025-04-08  6:22 ` Patrick Steinhardt
2025-04-08 14:50   ` Junio C Hamano
2025-04-09 11:31     ` Philippe Blain [this message]
2025-04-09 15:59       ` Junio C Hamano
2025-04-08  8:20 ` Karthik Nayak
2025-04-09 11:24 ` Philippe Blain
2025-04-09 16:01   ` Junio C Hamano
2025-06-05 12:51   ` Junio C Hamano
2025-06-05 15:10     ` Philippe Blain
2025-06-05 18:29       ` 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=d5588a3d-db07-5c4e-3c22-ad4b751dd3fc@gmail.com \
    --to=levraiphilippeblain@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=ps@pks.im \
    /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).