From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org, Derrick Stolee <stolee@gmail.com>,
shejialuo <shejialuo@gmail.com>
Subject: Re: What's cooking in git.git (Jan 2025, #04; Tue, 14)
Date: Thu, 16 Jan 2025 08:48:39 -0800 [thread overview]
Message-ID: <xmqqfrliu2l4.fsf@gitster.g> (raw)
In-Reply-To: <Z4jeQSLmARruE5l3@pks.im> (Patrick Steinhardt's message of "Thu, 16 Jan 2025 11:24:01 +0100")
Patrick Steinhardt <ps@pks.im> writes:
>> * ds/backfill (2024-12-20) 6 commits
>> ...
>> source: <pull.1820.v2.git.1734712193.gitgitgadget@gmail.com>
>
> I had a couple of nits and expect another reroll, but think it's close
> to being ready.
Yeah, this one is looking better.
A new command with a new test script means it requires a bit of
meson.build adjustment but I think that is well under control.
>> * ds/path-walk-1 (2024-12-20) 7 commits
>> ...
>> source: <pull.1818.v4.git.1734711675.gitgitgadget@gmail.com>
>
> I had a single nit, but don't necessarily think that it needs to be
> addressed.
Thanks.
prev parent reply other threads:[~2025-01-16 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-14 18:25 What's cooking in git.git (Jan 2025, #04; Tue, 14) Junio C Hamano
2025-01-16 10:24 ` Patrick Steinhardt
2025-01-16 16:48 ` Junio C Hamano [this message]
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=xmqqfrliu2l4.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
--cc=shejialuo@gmail.com \
--cc=stolee@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).