From: "brian m. carlson" <sandals@crustytoothpaste•net>
To: "Michal Suchánek" <msuchanek@suse•de>
Cc: Taylor Blau <me@ttaylorr•com>, git@vger•kernel.org
Subject: Re: When should we release Git 3.0?
Date: Wed, 1 Oct 2025 22:16:40 +0000 [thread overview]
Message-ID: <aN2oSBz8s_hSBMPq@fruit.crustytoothpaste.net> (raw)
In-Reply-To: <aN1UtbJRIhgvMmaF@kitsune.suse.cz>
[-- Attachment #1: Type: text/plain, Size: 1396 bytes --]
On 2025-10-01 at 16:20:05, Michal Suchánek wrote:
> From my very limited point of view as a user the interop is the major
> planned feature currently missing in git, and I do not see much point
> without it. Then again I do not know how useful it will be in practice.
It is the major planned feature which was missing.
The primary use cases are converting repositories and working with
repositories using a different algorithm. The latter might be useful if
you're using a SHA-256 repository that someone else has created but your
tooling cannot handle longer object IDs or otherwise has some limitation
of that sort.
If you are happy working with SHA-1 repositories in SHA-1 and SHA-256
repositories in SHA-256, then you don't need the interoperability work.
SHA-256 repositories have been supported in a compatible way since 2.29
or 2.30.
> Then again cloning a repository uses the correct hash which means if I
> create the repository on the forge and clone it there is no problem
> whatsoever regardless of hash used. Whill that break as well?
Cloning a repository always uses the existing algorithm. The default
would change to create _new_ repositories created with `git init` with
SHA-256 (although you could change the settings to use SHA-1 instead),
but it wouldn't affect existing repositories.
--
brian m. carlson (they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2025-10-01 22:16 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-30 23:07 When should we release Git 3.0? brian m. carlson
2025-10-01 7:13 ` Luca Milanesio
2025-10-01 16:04 ` Taylor Blau
2025-10-01 19:31 ` rsbecker
2025-10-08 21:44 ` Taylor Blau
2025-10-08 21:55 ` rsbecker
2025-10-02 13:31 ` Patrick Steinhardt
2025-10-02 15:32 ` Junio C Hamano
2025-10-02 16:10 ` Michal Suchánek
2025-10-07 10:27 ` Patrick Steinhardt
2025-10-07 10:36 ` Michal Suchánek
2025-10-07 13:21 ` Patrick Steinhardt
2025-10-07 13:40 ` Michal Suchánek
2025-10-07 17:11 ` Junio C Hamano
2025-10-07 17:28 ` Michal Suchánek
2025-10-08 20:44 ` SZEDER Gábor
2025-10-09 5:56 ` Patrick Steinhardt
2025-10-02 16:54 ` Ben Knoble
2025-10-07 10:27 ` Patrick Steinhardt
2025-10-07 17:36 ` rsbecker
2025-10-08 22:05 ` Taylor Blau
2025-10-09 5:59 ` Patrick Steinhardt
2025-10-16 21:32 ` brian m. carlson
2025-10-08 21:59 ` Taylor Blau
2025-10-16 21:42 ` brian m. carlson
2025-10-02 22:33 ` brian m. carlson
2025-10-01 16:01 ` Taylor Blau
2025-10-01 16:20 ` Michal Suchánek
2025-10-01 22:16 ` brian m. carlson [this message]
2025-10-02 12:13 ` Michal Suchánek
2025-10-02 13:09 ` Michal Suchánek
2025-10-01 20:36 ` Junio C Hamano
2025-10-01 22:42 ` brian m. carlson
-- strict thread matches above, loose matches on Subject: below --
2025-10-08 19:06 James Frost
2025-10-09 5:30 ` Patrick Steinhardt
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=aN2oSBz8s_hSBMPq@fruit.crustytoothpaste.net \
--to=sandals@crustytoothpaste$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=me@ttaylorr$(echo .)com \
--cc=msuchanek@suse$(echo .)de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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