public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed

From: Junio C Hamano <gitster@pobox•com>
To: Taylor Blau <me@ttaylorr•com>
Cc: git@vger•kernel.org
Subject: Re: What's cooking in git.git (Nov 2024, #07; Wed, 20)
Date: Fri, 22 Nov 2024 13:34:48 +0900	[thread overview]
Message-ID: <xmqqr073antj.fsf@gitster.g> (raw)
In-Reply-To: <Zz4Q+2X3wXhLO6FE@nand.local> (Taylor Blau's message of "Wed, 20 Nov 2024 11:40:27 -0500")

Taylor Blau <me@ttaylorr•com> writes:

> One topic I did not see is [1], which appeared not to be picked up in
> this or the last cycle. That topic has been reviewed and should be in
> good shape. I think the thread died down after agreeing on some
> potentially interesting future improvements we could make, but I don't
> think there were any outstanding issues with the current patches.

I didn't get the impression that there was a general concensus that
it was a good implementation, but perhaps I am misremembering things.

These two patches touch only the test helpers, but I am wondering if
it becomes easier to implement on top of your later changes that
allows the production side to also access the unsafe variant of the
algorithm?

Thanks.

next prev parent reply	other threads:[~2024-11-22  4:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-20  8:49 What's cooking in git.git (Nov 2024, #07; Wed, 20) Junio C Hamano
2024-11-20 10:36 ` Patrick Steinhardt
2024-11-20 13:41   ` shejialuo
2024-11-21  1:10   ` Junio C Hamano
2024-11-20 10:39 ` karthik nayak
2024-11-20 16:40 ` Taylor Blau
2024-11-21  0:44   ` Junio C Hamano
2024-11-22  4:34   ` Junio C Hamano [this message]
2024-11-21  8:26 ` Kristoffer Haugsbakk
2024-11-21 12:59   ` Junio C Hamano
2024-11-21 15:31     ` Kristoffer Haugsbakk
2024-11-21 23:11       ` 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=xmqqr073antj.fsf@gitster.g \
    --to=gitster@pobox$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=me@ttaylorr$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox