From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, Benno Evers <benno.martin.evers@gmail.com>,
Rasmus Villemoes <ravi@prevas.dk>,
Benno Evers <benno@bmevers.de>,
Josh Poimboeuf <jpoimboe@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>
Subject: Re: [PATCH 0/4] perf improvements for git-describe with few tags
Date: Tue, 26 Nov 2024 14:05:22 +0900 [thread overview]
Message-ID: <xmqqldx61t65.fsf@gitster.g> (raw)
In-Reply-To: <20241106192236.GC880133@coredump.intra.peff.net> (Jeff King's message of "Wed, 6 Nov 2024 14:22:36 -0500")
Jeff King <peff@peff.net> writes:
> So here's the series I came up with, which starts by adjusting the tests
> to be resilient to the later changes, but also to show the existing
> failure mode.
>
> And then the rest of the patches add the performance improvements we've
> been discussing in the thread.
So, this did not get any comments, but I had a time to read it over,
and did not find anything suspicious in there.
Let me mark it for 'next', this time for real, in the What's cooking
draft I have.
Thanks.
next prev parent reply other threads:[~2024-11-26 5:05 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <309549cafdcfe50c4fceac3263220cc3d8b109b2.1730337435.git.jpoimboe@kernel.org>
2024-10-31 10:37 ` [PATCH] setlocalversion: Add workaround for "git describe" performance issue Rasmus Villemoes
2024-10-31 11:42 ` Jeff King
2024-10-31 12:24 ` Jeff King
2024-10-31 14:43 ` Jeff King
2024-11-04 12:37 ` Benno Evers
2024-11-06 19:22 ` [PATCH 0/4] perf improvements for git-describe with few tags Jeff King
2024-11-06 19:26 ` Jeff King
2024-11-06 21:16 ` [PATCH 1/4] t6120: demonstrate weakness in disjoint-root handling Jeff King
2024-11-06 21:17 ` [PATCH 2/4] t/perf: add tests for git-describe Jeff King
2024-11-06 21:17 ` [PATCH 3/4] describe: stop digging for max_candidates+1 Jeff King
2024-11-06 21:17 ` [PATCH 4/4] describe: stop traversing when we run out of names Jeff King
2024-12-04 23:15 ` [PATCH] fixup! " Josh Steadmon
2024-12-04 23:27 ` Jeff King
2024-12-04 23:54 ` Jeff King
2024-12-05 20:14 ` [PATCH] describe: drop early return for max_candidates == 0 Jeff King
2024-12-05 22:28 ` Josh Steadmon
2024-12-05 23:21 ` Jeff King
2024-12-06 3:01 ` Junio C Hamano
2024-12-06 3:28 ` Jeff King
2024-12-06 4:19 ` Junio C Hamano
2024-12-06 5:42 ` [PATCH] describe: split "found all tags" and max_candidates logic Jeff King
2024-11-26 5:05 ` Junio C Hamano [this message]
2024-12-04 23:04 ` [PATCH 0/4] perf improvements for git-describe with few tags Josh Steadmon
2024-12-04 23:20 ` Jeff King
2024-11-01 10:23 ` [PATCH] setlocalversion: Add workaround for "git describe" performance issue Rasmus Villemoes
2024-11-01 11:39 ` Jeff King
2024-10-31 11:43 ` Masahiro Yamada
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=xmqqldx61t65.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=benno.martin.evers@gmail.com \
--cc=benno@bmevers.de \
--cc=git@vger.kernel.org \
--cc=jpoimboe@kernel.org \
--cc=masahiroy@kernel.org \
--cc=peff@peff.net \
--cc=ravi@prevas.dk \
/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).