From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2026, #03)
Date: Sun, 08 Feb 2026 16:55:51 -0800 [thread overview]
Message-ID: <xmqqv7g67n1k.fsf@gitster.g> (raw)
In-Reply-To: <aYkX3rIkpIvLsej0@fruit.crustytoothpaste.net> (brian m. carlson's message of "Sun, 8 Feb 2026 23:10:22 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> On 2026-02-07 at 23:15:51, Junio C Hamano wrote:
>> * bc/sha1-256-interop-02 (2025-11-17) 15 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
>> - 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.
>>
>> Any progress on CI breakages???
>> source: <20251117221621.2863243-1-sandals@crustytoothpaste.net>
>
> I just sent v3 yesterday which fixes the CI breakages.
Yup, I replaced the topic with the latest one, and the draft for the
next issue of "What's cooking" has this entry updated already.
Thanks.
* 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.
Comments? v1 saw a lot of discussions, v2 didn't, and this is v3,
which is essentially identical to v2 with CI fixes (which work!).
source: <20260207200446.2837699-1-sandals@crustytoothpaste.net>
next prev parent reply other threads:[~2026-02-09 0:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-07 23:15 What's cooking in git.git (Feb 2026, #03) Junio C Hamano
2026-02-08 21:13 ` Kristoffer Haugsbakk
2026-02-08 23:10 ` brian m. carlson
2026-02-09 0:55 ` Junio C Hamano [this message]
2026-02-09 9:14 ` Patrick Steinhardt
2026-02-09 16:37 ` Junio C Hamano
2026-02-09 19:41 ` Ramsay Jones
2026-02-10 13:26 ` Patrick Steinhardt
2026-02-10 19:06 ` Ramsay Jones
2026-02-09 9:52 ` Adrian Ratiu
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=xmqqv7g67n1k.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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