public inbox for git@vger.kernel.org
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Junio C Hamano <junio@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Jan 2026, #09)
Date: Wed, 28 Jan 2026 22:50:50 +0000	[thread overview]
Message-ID: <aXqSyn3Mfcgs8MUG@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <xmqqecnbeyvr.fsf@gitster.g>

[-- Attachment #1: Type: text/plain, Size: 1540 bytes --]

On 2026-01-27 at 17:42:00, 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>

Not yet, but I hope to spend some time on that this week or early next.
I now have some more time to work on this at work and I can try to poke
around and figure out what might be wrong, or at least try to beg a
colleague to try things on their Windows VM.

My apologies for the delay; things have been busy lately and I've had
less personal time to work on Git.
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

  parent reply	other threads:[~2026-01-28 22:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27 17:42 What's cooking in git.git (Jan 2026, #09) Junio C Hamano
2026-01-27 22:03 ` Taylor Blau
2026-02-06 19:39   ` Junio C Hamano
2026-01-28 14:29 ` ds/revision-maximal-only (was Re: What's cooking in git.git (Jan 2026, #09)) Derrick Stolee
2026-01-28 22:50 ` brian m. carlson [this message]
2026-01-29 22:01   ` What's cooking in git.git (Jan 2026, #09) brian m. carlson
2026-01-29 22:51     ` Eric Sunshine
2026-01-29 23:25       ` brian m. carlson

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=aXqSyn3Mfcgs8MUG@fruit.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=junio@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