From: "Michal Suchánek" <msuchanek@suse•de>
To: Junio C Hamano <gitster@pobox•com>
Cc: Patrick Steinhardt <ps@pks•im>, Taylor Blau <me@ttaylorr•com>,
Luca Milanesio <luca.milanesio@gmail•com>,
git@vger•kernel.org
Subject: Re: When should we release Git 3.0?
Date: Tue, 7 Oct 2025 19:28:03 +0200 [thread overview]
Message-ID: <aOVNozn-ycPoLf2p@kitsune.suse.cz> (raw)
In-Reply-To: <xmqqv7kqk56r.fsf@gitster.g>
On Tue, Oct 07, 2025 at 10:11:24AM -0700, Junio C Hamano wrote:
> Patrick Steinhardt <ps@pks•im> writes:
>
> > On Tue, Oct 07, 2025 at 12:36:47PM +0200, Michal Suchánek wrote:
> >> On Tue, Oct 07, 2025 at 12:27:23PM +0200, Patrick Steinhardt wrote:
> >> > The question of course is how to get such roadmaps. The easiest way to
> >> > do it is probably to gather a list of known projects that would be
> >> > impacted and just shoot maintainers or representatives of those an
> >> > email? From the top of my head, that would include:
> >> >
> >> > - Implementations
> >> > - libgit2
> >> - pygit2
> >> > - JGit
> >> > - Gitoxide
> >> > - go-git
> >
> > pygit2 is merely a binding for libgit2, so I didn't include it in this
> > list. Same for other bindings like git2go or git2-rs.
>
> Is dulwich still alive?
Interesting, did not know it exists (also abysmal SEO, not surprising).
Its web page seems unmaintained but the git repository looks alive.
Thanks
Michal
>
> >
> >> > - Forges
> >> > - GitHub
> >> > - GitLab
> >> > - Bitbucket
> >> > - Forgejo
> >> - Gitea
> >> > - SourceHut
> >
> > Yup, this one should be included here indeed.
> >
> > Thanks!
> >
> > Patrick
next prev parent reply other threads:[~2025-10-07 17:28 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 [this message]
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=aOVNozn-ycPoLf2p@kitsune.suse.cz \
--to=msuchanek@suse$(echo .)de \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=luca.milanesio@gmail$(echo .)com \
--cc=me@ttaylorr$(echo .)com \
--cc=ps@pks$(echo .)im \
/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