From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2024, #06; Thu, 14)
Date: Fri, 15 Nov 2024 22:19:04 -0500 [thread overview]
Message-ID: <20241116031904.GA1782074@coredump.intra.peff.net> (raw)
In-Reply-To: <xmqqy11kys9z.fsf@gitster.g>
On Sat, Nov 16, 2024 at 08:46:32AM +0900, Junio C Hamano wrote:
> * jk/describe-perf (2024-11-07) 4 commits
> - describe: stop traversing when we run out of names
> - describe: stop digging for max_candidates+1
> - t/perf: add tests for git-describe
> - t6120: demonstrate weakness in disjoint-root handling
>
> "git describe" optimization.
>
> Expecting a reroll.
> cf <20241106192650.GA912471@coredump.intra.peff.net>
> source: <20241106192236.GC880133@coredump.intra.peff.net>
I wasn't planning on any re-roll here. I think I may have confused you
when I sent out the cover letter, followed up with a "oops there's a
small fixup I need, I'll send out the patches later today" message, and
then later sent out the patches. That "v1" that hit the list (and what
you picked up) is the fixed version.
So there is nothing to re-roll, as there haven't been any comments on
it. Possibly "needs review" would be a better label. :)
-Peff
next prev parent reply other threads:[~2024-11-16 3:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 23:46 What's cooking in git.git (Nov 2024, #06; Thu, 14) Junio C Hamano
2024-11-16 3:19 ` Jeff King [this message]
2024-11-16 9:37 ` Junio C Hamano
2024-11-16 11:24 ` Patrick Steinhardt
2024-11-16 15:37 ` Rubén Justo
2024-11-18 6:42 ` Patrick Steinhardt
2024-11-18 22:20 ` Rubén Justo
2024-11-16 14:57 ` Kristoffer Haugsbakk
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=20241116031904.GA1782074@coredump.intra.peff.net \
--to=peff@peff.net \
--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