From: Junio C Hamano <gitster@pobox.com>
To: "D. Ben Knoble" <ben.knoble@gmail.com>
Cc: Usman Akinyemi <usmanakinyemi202@gmail.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jul 2025, #07; Thu, 24)
Date: Sat, 26 Jul 2025 17:00:40 -0700 [thread overview]
Message-ID: <xmqq5xfe1p07.fsf@gitster.g> (raw)
In-Reply-To: <CALnO6CD58LMgGgxGF1DRheeFe-E9zRwAKG=-qsUO=kDB-gTdeg@mail.gmail.com> (D. Ben Knoble's message of "Sat, 26 Jul 2025 09:00:26 -0400")
"D. Ben Knoble" <ben.knoble@gmail.com> writes:
>> Is there something that needs to be done here ?
>
> I would interpret "introduce a few 'todo passed' when merged to
> 'seen'" to mean that a few test_expect_failure's are now passing and
> need updating.
Thanks for helping.
next prev parent reply other threads:[~2025-07-27 0:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 17:18 What's cooking in git.git (Jul 2025, #07; Thu, 24) Junio C Hamano
2025-07-26 2:03 ` Usman Akinyemi
2025-07-26 13:00 ` D. Ben Knoble
2025-07-27 0:00 ` Junio C Hamano [this message]
2025-07-26 17:45 ` Junio C Hamano
2025-07-26 21:27 ` Usman Akinyemi
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=xmqq5xfe1p07.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble@gmail.com \
--cc=git@vger.kernel.org \
--cc=usmanakinyemi202@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).