Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Kristofer Karlsson <krka@spotify.com>
Cc: "René Scharfe" <l.s.r@web.de>,
	"Kristofer Karlsson via GitGitGadget" <gitgitgadget@gmail.com>,
	git@vger.kernel.org
Subject: Re: [PATCH v2] prio-queue: use cascade-down for faster extract-min
Date: Mon, 29 Jun 2026 14:16:11 -0700	[thread overview]
Message-ID: <xmqqv7b1t5d0.fsf@gitster.g> (raw)
In-Reply-To: <CAL71e4MYNiScZjTwkApjDAjRh2LM0_SP59h5HCTywV-Pua03tw@mail.gmail.com> (Kristofer Karlsson's message of "Sun, 7 Jun 2026 14:07:21 +0200")

Kristofer Karlsson <krka@spotify.com> writes:

> Now I am thinking it would be easier to reason about this if the other
> patch lands first, since the cascade change becomes simpler to evaluate
> when replace is already gone and only the unfused paths remain.

Sorry, I should have noticed this message and responded earlier.
Let's make sure that the "other patch" is ready then and merge it
down.

Since June 8th, nothing seemed to have happened to the thread for
the "other patch".

  https://lore.kernel.org/git/pull.2140.v4.git.1780945851.gitgitgadget@gmail.com/

Is everybody happy with these two patches?

Thanks.

  reply	other threads:[~2026-06-29 21:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-31 17:57 [PATCH] prio-queue: use cascade-down sift for faster extract-min Kristofer Karlsson via GitGitGadget
2026-06-01  0:09 ` Junio C Hamano
2026-06-01  6:16 ` Junio C Hamano
2026-06-01  6:21   ` Kristofer Karlsson
2026-06-01  8:17 ` [PATCH v2] prio-queue: use cascade-down " Kristofer Karlsson via GitGitGadget
2026-06-02 16:36   ` René Scharfe
2026-06-02 22:40     ` Kristofer Karlsson
2026-06-05 20:39       ` Kristofer Karlsson
2026-06-07  7:30         ` René Scharfe
2026-06-07 12:07           ` Kristofer Karlsson
2026-06-29 21:16             ` Junio C Hamano [this message]
2026-06-08 11:56           ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqv7b1t5d0.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=gitgitgadget@gmail.com \
    --cc=krka@spotify.com \
    --cc=l.s.r@web.de \
    /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