git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Taylor Blau <me@ttaylorr.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2024, #05; Fri, 13)
Date: Mon, 16 Sep 2024 15:39:57 -0400	[thread overview]
Message-ID: <ZuiJjQCZ23DznwJo@nand.local> (raw)
In-Reply-To: <xmqqwmjerqvl.fsf@gitster.g>

On Sat, Sep 14, 2024 at 12:12:46PM -0700, Junio C Hamano wrote:
> * tb/weak-sha1-for-tail-sum (2024-09-06) 9 commits
>  - csum-file.c: use fast SHA-1 implementation when available
>  - Makefile: allow specifying a SHA-1 for non-cryptographic uses
>  - hash.h: scaffolding for _fast hashing variants
>  - sha1: do not redefine `platform_SHA_CTX` and friends
>  - i5500-git-daemon.sh: use compile-able version of Git without OpenSSL
>  - pack-objects: use finalize_object_file() to rename pack/idx/etc
>  - finalize_object_file(): implement collision check
>  - finalize_object_file(): refactor unlink_or_warn() placement
>  - finalize_object_file(): check for name collision before renaming
>
>  The checksum at the tail of files are now computed without
>  collision detection protection.
>
>  Will merge to 'next'?
>  source: <cover.1725651952.git.me@ttaylorr.com>

Let's hold off on this one. Patrick raised a good point in [1] that I
think I have a fix for, but want to hear some further discussion before
I convince myself that's the case.

Thanks,
Taylor

[1]: https://lore.kernel.org/git/ZugMUv1xbnjYH-el@pks.im/

  reply	other threads:[~2024-09-16 19:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-14 19:12 What's cooking in git.git (Sep 2024, #05; Fri, 13) Junio C Hamano
2024-09-16 19:39 ` Taylor Blau [this message]
2024-09-17  6:30   ` Patrick Steinhardt
2024-09-17  8:17     ` Taylor Blau
2024-09-17  9:27       ` Patrick Steinhardt
2024-09-17  9:31         ` Taylor Blau

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=ZuiJjQCZ23DznwJo@nand.local \
    --to=me@ttaylorr.com \
    --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;
as well as URLs for NNTP newsgroup(s).