From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2026, #01)
Date: Wed, 4 Mar 2026 00:13:36 +0000 [thread overview]
Message-ID: <aad5MGUt8ZVdxLlY@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <xmqqbjh5fvsn.fsf@gitster.g>
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
On 2026-03-03 at 03:15:20, Junio C Hamano wrote:
> * bc/sha1-256-interop-02 (2026-02-07) 16 commits
> - object-file-convert: always make sure object ID algo is valid
> - rust: add a small wrapper around the hashfile code
> - rust: add a new binary object map format
> - rust: add functionality to hash an object
> - rust: add a build.rs script for tests
> - rust: fix linking binaries with cargo
> - hash: expose hash context functions to Rust
> - write-or-die: add an fsync component for the object map
> - csum-file: define hashwrite's count as a uint32_t
> - rust: add additional helpers for ObjectID
> - hash: add a function to look up hash algo structs
> - rust: add a hash algorithm abstraction
> - rust: add a ObjectID struct
> - hash: use uint32_t for object_id algorithm
> - conversion: don't crash when no destination algo
> - repository: require Rust support for interoperability
>
> The code to maintain mapping between object names in multiple hash
> functions is being added, written in Rust.
>
> Will merge to 'next'?
> Message-Id: <20260207200446.2837699-1-sandals@crustytoothpaste.net>
I think this is ready. Of course, if others have objections, I can make
changes.
--
brian m. carlson (they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
prev parent reply other threads:[~2026-03-04 0:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 3:15 What's cooking in git.git (Mar 2026, #01) Junio C Hamano
2026-03-03 18:10 ` Derrick Stolee
2026-03-03 18:43 ` Junio C Hamano
2026-03-04 0:13 ` brian m. carlson [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=aad5MGUt8ZVdxLlY@fruit.crustytoothpaste.net \
--to=sandals@crustytoothpaste.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