git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 0/4] hash: introduce generic wrappers to update hash contexts
Date: Mon, 10 Feb 2025 17:55:10 -0500	[thread overview]
Message-ID: <Z6qDzscMzRyoIiz1@nand.local> (raw)
In-Reply-To: <20250131-b4-pks-hash-context-direct-v1-0-67a6d3f49d6e@pks.im>

On Fri, Jan 31, 2025 at 01:55:27PM +0100, Patrick Steinhardt wrote:
> ---
> Patrick Steinhardt (4):
>       hash: convert hashing context to a structure
>       hash: stop typedeffing the hash context
>       hash: provide generic wrappers to update hash contexts
>       global: adapt callers to use generic hash context helpers

Catching up through some emails that I had missed, and this series looks
great to me. I'm really glad that you ended up pulling on this thread a
little more, and the result is quite pleasing.

Junio has already marked this as "Will merge to 'master'" in the latest
WC, and I have no objections to that ;-).

Thanks,
Taylor

      parent reply	other threads:[~2025-02-10 22:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-31 12:55 [PATCH 0/4] hash: introduce generic wrappers to update hash contexts Patrick Steinhardt
2025-01-31 12:55 ` [PATCH 1/4] hash: convert hashing context to a structure Patrick Steinhardt
2025-01-31 12:55 ` [PATCH 2/4] hash: stop typedeffing the hash context Patrick Steinhardt
2025-01-31 12:55 ` [PATCH 3/4] hash: provide generic wrappers to update hash contexts Patrick Steinhardt
2025-01-31 12:55 ` [PATCH 4/4] global: adapt callers to use generic hash context helpers Patrick Steinhardt
2025-01-31 18:16 ` [PATCH 0/4] hash: introduce generic wrappers to update hash contexts Junio C Hamano
2025-02-03  5:42   ` Patrick Steinhardt
2025-02-10 22:55 ` Taylor Blau [this message]

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=Z6qDzscMzRyoIiz1@nand.local \
    --to=me@ttaylorr.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=ps@pks.im \
    /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).