git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Philippe Blain <levraiphilippeblain@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2025, #03; Fri, 11)
Date: Sat, 12 Apr 2025 22:55:55 -0400	[thread overview]
Message-ID: <4b8dce0b-9159-4793-2da6-ddeb230d333a@gmail.com> (raw)
In-Reply-To: <5a257012-39ff-80af-7d65-029ec250a321@gmail.com>

Le 2025-04-12 à 14:03, Philippe Blain a écrit :
> Hi Junio,
> 
> Le 2025-04-11 à 18:58, Junio C Hamano a écrit :
> 
>> * pb/perf-test-fixes (2025-03-28) 2 commits
>>   (merged to 'next' on 2025-04-08 at a8aaeee41e)
>>  + p9210: fix 'scalar clone' when running from a detached HEAD
>>  + p7821: fix test_perf invocation for prereqs
>>
>>  "make perf" fixes.
>>
>>  Will merge to 'master'.
>>  cf. <Z-pD1puYT87YKAd4@pks.im>
>>  cf. <Z_TAtJ9LEeHo2AQN@pks.im>
>>  source: <pull.1936.git.git.1743181669.gitgitgadget@gmail.com>
> 
> I actually found a small error in the comment at the top of p7821,
> I'll send a new version with a 3rd commit on top.

v2 is here, the only difference is an additional commit
fixing this comment:

https://lore.kernel.org/git/abd146b7c2a62aaef5c22269cff155387f33fe32.1744481732.git.gitgitgadget@gmail.com/

  reply	other threads:[~2025-04-13  2:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11 22:58 What's cooking in git.git (Apr 2025, #03; Fri, 11) Junio C Hamano
2025-04-12 18:03 ` Philippe Blain
2025-04-13  2:55   ` Philippe Blain [this message]
2025-04-14 13:04   ` Junio C Hamano
2025-04-14  8:13 ` Patrick Steinhardt
2025-04-14 13:34   ` Junio C Hamano
2025-04-14 20:14   ` [-SPAM-] " Ramsay Jones
2025-04-14 11:03 ` ds/path-walk-2 (was Re: What's cooking in git.git (Apr 2025, #03; Fri, 11)) Derrick Stolee
2025-04-14 12:34   ` 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=4b8dce0b-9159-4793-2da6-ddeb230d333a@gmail.com \
    --to=levraiphilippeblain@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).