From: Taylor Blau <me@ttaylorr.com>
To: rsbecker@nexbridge.com
Cc: 'Luca Milanesio' <luca.milanesio@gmail.com>, git@vger.kernel.org
Subject: Re: When should we release Git 3.0?
Date: Wed, 8 Oct 2025 17:44:56 -0400 [thread overview]
Message-ID: <aObbWLBCbXsvuajS@nand.local> (raw)
In-Reply-To: <04f501dc330a$0ecd3010$2c679030$@nexbridge.com>
On Wed, Oct 01, 2025 at 03:31:54PM -0400, rsbecker@nexbridge.com wrote:
> On October 1, 2025 12:05 PM, Taylor Blau wrote:
> >On Wed, Oct 01, 2025 at 08:13:12AM +0100, Luca Milanesio wrote:
> >> I am worried that if we rush into Git 3.0 with breaking changes that
> >> would make other “forges” (e.g. JGit) incompatible, we would be in a
> >> difficult situation with the other Git ecosystem that isn’t based on
> >> the C-Git implementation.
> >
> >That's a good point. I am not familiar enough with JGit (or really any non-standard
> >Git implementations) to know where SHA-256 support is in those respective
> >implementations.
>
> AFAIK, JGit still depends on some core git functions, including gc. It
> also depends on LFS for those functions. Interop it fairly important
> in that space.
What are "core git functions" here? I'm not at all familiar with JGit,
but my understanding is that it doesn't use the Git binary directly
whatsoever, so I am not sure how the presence of interop support or not
would affect JGit or LFS.
Thanks,
Taylor
next prev parent reply other threads:[~2025-10-08 21:44 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 [this message]
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
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=aObbWLBCbXsvuajS@nand.local \
--to=me@ttaylorr.com \
--cc=git@vger.kernel.org \
--cc=luca.milanesio@gmail.com \
--cc=rsbecker@nexbridge.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).