From: Jeff King <peff@peff•net>
To: 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣 <velocifyer@velocifyer•com>
Cc: git@vger•kernel.org
Subject: Re: How do i get news of git releases
Date: Mon, 22 Sep 2025 16:14:03 -0400 [thread overview]
Message-ID: <20250922201403.GD2205919@coredump.intra.peff.net> (raw)
In-Reply-To: <4ea9cb1e-4367-4926-a9ba-0680dd63e616@velocifyer.com>
On Mon, Sep 22, 2025 at 01:43:31PM -0400, 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣 wrote:
> How do i get changelogs for git in a convinent format (like email or RSS or
> Atom)? I see that i can get changelogs in /Documentation/RelNotes/ but then
> i have to check the folder manually instead of it being in my email and RSS
> and Atom client (Thunderbird).
The Git project doesn't maintain any RSS feeds that I'm aware of.
However, releases are pushed to GitHub (among many other mirrors), and
they do provide feeds. So I think pointing your feed-reader at:
https://github.com/git/git/releases.atom
would work.
The project doesn't use GitHub's Releases feature specifically, but I
think annotated tags that are pushed to the repo end up there, too. The
resulting feed entries are a little bare. Possibly they could be
populated with the release notes, but from the Git project's
perspective, the GitHub repo is really just a Git mirror. Presumably it
would require some scripting around GitHub's API for the tag pushes to
also create Release entries (and then probably somebody would want the
same for the GitLab mirror, and so on).
I think it may also be a reasonable feature for git-scm.com to have its
own RSS feed. It already has to know about all of the releases (so it
can point to the most recent one, for example). Most of the development
for that site happens at https://github.com/git/git-scm.com. So if you
or anybody is interested in adding the feature, it would probably make
sense to start a discussion there.
-Peff
next prev parent reply other threads:[~2025-09-22 20:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 17:43 How do i get news of git releases 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣
2025-09-22 20:14 ` Jeff King [this message]
[not found] ` <1ff96277-c9e7-483e-ac98-b109b9603475@velocifyer.com>
2025-09-22 20:38 ` Jeff King
2025-09-22 21:16 ` Junio C Hamano
2025-09-22 21:35 ` Jeff King
2025-09-22 21:05 ` Junio C Hamano
2025-09-23 9:43 ` Christian Couder
2025-09-23 19:41 ` 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣
2025-09-24 8:38 ` Christian Couder
2025-09-24 18:51 ` Junio C Hamano
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=20250922201403.GD2205919@coredump.intra.peff.net \
--to=peff@peff$(echo .)net \
--cc=git@vger$(echo .)kernel.org \
--cc=velocifyer@velocifyer$(echo .)com \
/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