From: James Frost <james@frost•cx>
To: msuchanek@suse•de
Cc: git@vger•kernel.org, gitster@pobox•com, luca.milanesio@gmail•com,
me@ttaylorr•com, ps@pks•im
Subject: Re: When should we release Git 3.0?
Date: Wed, 8 Oct 2025 20:06:18 +0100 [thread overview]
Message-ID: <d3f49610-bd19-4bbf-a3ec-c15be2c07338@frost.cx> (raw)
> - Implementations
> - libgit2
> - pygit2
> - JGit
> - Gitoxide
> - go-git
> - Forges
> - GitHub
> - GitLab
> - Bitbucket
> - Forgejo
> - Gitea
> - SourceHut
- Frontends
- gitweb
- cgit
Should we also consider other frontends, such as gitweb[^1] and cgit[^2]?
[^1]: https://git-scm.com/docs/gitweb
[^2]: https://git.zx2c4.com/cgit/about/
next reply other threads:[~2025-10-08 19:06 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 19:06 James Frost [this message]
2025-10-09 5:30 ` When should we release Git 3.0? Patrick Steinhardt
-- strict thread matches above, loose matches on Subject: below --
2025-09-30 23:07 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
2025-10-01 20:36 ` Junio C Hamano
2025-10-01 22:42 ` brian m. carlson
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=d3f49610-bd19-4bbf-a3ec-c15be2c07338@frost.cx \
--to=james@frost$(echo .)cx \
--cc=aOTtPxsdzJLPCruk@kitsune$(echo .)suse.cz \
--cc=git@vger$(echo .)kernel.org \
--cc=gitster@pobox$(echo .)com \
--cc=luca.milanesio@gmail$(echo .)com \
--cc=me@ttaylorr$(echo .)com \
--cc=msuchanek@suse$(echo .)de \
--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