From: "Michal Suchánek" <msuchanek@suse•de>
To: "brian m. carlson" <sandals@crustytoothpaste•net>,
Taylor Blau <me@ttaylorr•com>,
git@vger•kernel.org
Subject: Re: When should we release Git 3.0?
Date: Thu, 2 Oct 2025 15:09:52 +0200 [thread overview]
Message-ID: <aN55oCWX1l_VUuNh@kitsune.suse.cz> (raw)
In-Reply-To: <aN5sVXNdW8-GSMAE@kitsune.suse.cz>
On Thu, Oct 02, 2025 at 02:13:09PM +0200, Michal Suchánek wrote:
> On Wed, Oct 01, 2025 at 10:16:40PM +0000, brian m. carlson wrote:
> > 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.
>
> It cannot, and the compat will not help with that because it's using
> pygit which will not get that compat code. Presumably some baroque
> scheme that re-exports the repository as sha1 might be possible but it's
> not clear if that would be practical.
>
> Another problem people are comlaining about is that with a mix of sha1
> and sha256 repositories submodules and subtrees don't work. For that the
> compat might actually help but the repository will then be
> unintelligible to tooling that does not have compat code, which probably
> includes all forges at this point. Again, some baroque scheme that
> re-exports the repository in the other hash using the compat code might
> help but it's not clear if that would be practical.
I would assume the compat client could upload the same repository to
both sha256 forge repository and sha1 forge repository. With some
scripting it's possible to publish twice making both hashes available.
People that have a compat-capable client then would see the repositories
as identical again on their end.
Not usable in every situation but for cases when mirroring is already
done anyway plugging this in sounds fairly straightforward.
Thanks
Michal
next prev parent reply other threads:[~2025-10-02 13:09 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
2025-10-02 12:13 ` Michal Suchánek
2025-10-02 13:09 ` Michal Suchánek [this message]
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=aN55oCWX1l_VUuNh@kitsune.suse.cz \
--to=msuchanek@suse$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=me@ttaylorr$(echo .)com \
--cc=sandals@crustytoothpaste$(echo .)net \
/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