git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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 (Jul 2025, #02; Mon, 7)
Date: Wed, 9 Jul 2025 23:14:33 +0000	[thread overview]
Message-ID: <aG732RLqENitRwlv@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <xmqqplebzgm7.fsf@gitster.g>

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

On 2025-07-08 at 00:11:12, Junio C Hamano wrote:
> * bc/use-sha256-by-default-in-3.0 (2025-07-01) 11 commits
>  - Enable SHA-256 by default in breaking changes mode
>  - help: add a build option for default hash
>  - t5300: choose the built-in hash outside of a repo
>  - t4042: choose the built-in hash outside of a repo
>  - t1007: choose the built-in hash outside of a repo
>  - t: default to compile-time default hash if not set
>  - setup: use the default algorithm to initialize repo format
>  - Use legacy hash for legacy formats
>  - builtin: use default hash when outside a repository
>  - hash: add a constant for the legacy hash algorithm
>  - hash: add a constant for the default hash algorithm
> 
>  Prepare to flip the default hash function to SHA-256.
> 
>  Will merge to 'next'?
>  source: <20250701212237.766774-1-sandals@crustytoothpaste.net>

Patrick Steinhardt thought this looked fine and I didn't have any
intentions for another round, so I suspect it's ready.

Of course, if people disagree and would like more changes, please say
so.
-- 
brian m. carlson (they/them)
Toronto, Ontario, CA

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

  parent reply	other threads:[~2025-07-09 23:14 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-08  0:11 What's cooking in git.git (Jul 2025, #02; Mon, 7) Junio C Hamano
2025-07-08  0:47 ` Ayush Chandekar
2025-07-09  9:25 ` René Scharfe
2025-07-09 15:37   ` Junio C Hamano
2025-07-09 10:41 ` Carlo Marcelo Arenas Belón
2025-07-09 14:15   ` Phillip Wood
2025-07-09 15:04   ` Johannes Sixt
2025-07-10  4:25     ` Carlo Marcelo Arenas Belón
2025-07-10  7:18       ` Johannes Sixt
2025-07-10 15:30         ` Junio C Hamano
2025-07-09 16:26   ` Junio C Hamano
2025-07-09 14:46 ` Taylor Blau
2025-07-10  0:01   ` Junio C Hamano
2025-07-10  1:05     ` Elijah Newren
2025-07-10  4:24       ` Junio C Hamano
2025-07-09 23:14 ` brian m. carlson [this message]
2025-07-10  4:24   ` Junio C Hamano

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=aG732RLqENitRwlv@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;
as well as URLs for NNTP newsgroup(s).