From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: jl/subtree-check-parents-argument-passing-fix, was Re: What's cooking in git.git (Jan 2022, #01; Mon, 3)
Date: Tue, 04 Jan 2022 12:05:46 -0800 [thread overview]
Message-ID: <xmqqfsq3cllx.fsf@gitster.g> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.2201041322090.7076@tvgsbejvaqbjf.bet> (Johannes Schindelin's message of "Tue, 4 Jan 2022 13:23:58 +0100 (CET)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> Hi Junio,
>
> On Mon, 3 Jan 2022, Junio C Hamano wrote:
>
>> * jl/subtree-check-parents-argument-passing-fix (2021-12-05) 1 commit
>> - subtree: fix argument handling in check_parents
>>
>> Fix performance-releated bug in "git subtree" (in contrib/).
>>
>> Expecting a reroll.
>> cf. <nycvar.QRO.7.76.6.2112072243310.90@tvgsbejvaqbjf.bet>
>> source: <pull.1086.v3.git.1638758742741.gitgitgadget@gmail.com>
>
> James sent a v4 already four weeks ago, I just did not find time to look
> at it yet, before today. I offered my thumbs-up in the thread, and now I
> am offering it here, too: this patch is ready for prime time.
Thanks, I just saw your review on the latest one.
next prev parent reply other threads:[~2022-01-04 20:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 3:46 What's cooking in git.git (Jan 2022, #01; Mon, 3) Junio C Hamano
2022-01-04 12:23 ` jl/subtree-check-parents-argument-passing-fix, was " Johannes Schindelin
2022-01-04 20:05 ` Junio C Hamano [this message]
2022-01-04 13:59 ` lh/use-gnu-color-in-grep, " Johannes Schindelin
2022-01-04 18:06 ` Philippe Blain
2022-01-04 20:11 ` Junio C Hamano
2022-01-04 17:32 ` tb/midx-bitmap-corruption-fix (was: What's cooking in git.git (Jan 2022, #01; Mon, 3)) Taylor Blau
2022-01-04 20:13 ` tb/midx-bitmap-corruption-fix 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqfsq3cllx.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).