{"thread":{"id":"64182","subject":"How do i get news of git releases","startedAt":"2025-09-22T17:43:46Z","lastAt":"2025-09-24T18:51:21Z","messageCount":10,"participants":["𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣","Jeff King","Junio C Hamano","Christian Couder"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"526958","messageId":"4ea9cb1e-4367-4926-a9ba-0680dd63e616@velocifyer.com","threadId":"64182","inReplyTo":null,"subject":"How do i get news of git releases","fromName":"𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣","fromEmail":"velocifyer@velocifyer.com","sentAt":"2025-09-22T17:43:31Z","receivedAt":"2025-09-22T17:43:46Z","isPatch":false,"sender":{"key":"velocifyer@velocifyer.com","avatar":null},"body":"How do i get changelogs for git in a convinent format (like email or RSS \nor Atom)?  I see that i can get changelogs in /Documentation/RelNotes/ \nbut then i have to check the folder manually instead of it being in my \nemail and RSS and Atom client (Thunderbird).\n\n-- \nGeorge truly, 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣\nThis email does not constitute a legally binding contract ‮\n"},{"id":"526981","messageId":"20250922201403.GD2205919@coredump.intra.peff.net","threadId":"64182","inReplyTo":"4ea9cb1e-4367-4926-a9ba-0680dd63e616@velocifyer.com","subject":"Re: How do i get news of git releases","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2025-09-22T20:14:03Z","receivedAt":"2025-09-22T20:14:05Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Sep 22, 2025 at 01:43:31PM -0400, 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣 wrote:\n\n> How do i get changelogs for git in a convinent format (like email or RSS or\n> Atom)?  I see that i can get changelogs in /Documentation/RelNotes/ but then\n> i have to check the folder manually instead of it being in my email and RSS\n> and Atom client (Thunderbird).\n\nThe Git project doesn't maintain any RSS feeds that I'm aware of.\nHowever, releases are pushed to GitHub (among many other mirrors), and\nthey do provide feeds. So I think pointing your feed-reader at:\n\n https://github.com/git/git/releases.atom\n\nwould work.\n\nThe project doesn't use GitHub's Releases feature specifically, but I\nthink annotated tags that are pushed to the repo end up there, too. The\nresulting feed entries are a little bare. Possibly they could be\npopulated with the release notes, but from the Git project's\nperspective, the GitHub repo is really just a Git mirror. Presumably it\nwould require some scripting around GitHub's API for the tag pushes to\nalso create Release entries (and then probably somebody would want the\nsame for the GitLab mirror, and so on).\n\nI think it may also be a reasonable feature for git-scm.com to have its\nown RSS feed. It already has to know about all of the releases (so it\ncan point to the most recent one, for example). Most of the development\nfor that site happens at https://github.com/git/git-scm.com. So if you\nor anybody is interested in adding the feature, it would probably make\nsense to start a discussion there.\n\n-Peff\n"},{"id":"526983","messageId":"20250922203815.GA2264272@coredump.intra.peff.net","threadId":"64182","inReplyTo":"1ff96277-c9e7-483e-ac98-b109b9603475@velocifyer.com","subject":"Re: How do i get news of git releases","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2025-09-22T20:38:15Z","receivedAt":"2025-09-22T20:38:17Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"[please keep responses on-list]\n\nOn Mon, Sep 22, 2025 at 04:27:44PM -0400, 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣 wrote:\n\n> > The Git project doesn't maintain any RSS feeds that I'm aware of.\n> > However, releases are pushed to GitHub (among many other mirrors), and\n> > they do provide feeds. So I think pointing your feed-reader at:\n> > \n> > https://github.com/git/git/releases.atom\n> > \n> > would work.\n> > \n> > The project doesn't use GitHub's Releases feature specifically, but I\n> > think annotated tags that are pushed to the repo end up there, too. The\n> > resulting feed entries are a little bare. Possibly they could be\n> > populated with the release notes, but from the Git project's\n> > perspective, the GitHub repo is really just a Git mirror. Presumably it\n> > would require some scripting around GitHub's API for the tag pushes to\n> > also create Release entries (and then probably somebody would want the\n> > same for the GitLab mirror, and so on).\n> \n> Why do the Git tags not have the changelog? You can use git-tag -a to create\n> a tag with a changelog.\n\nYes, they're already annotated tags. But they contain only the version\nnumber and signature. I suppose they could include the whole set of\nrelease notes (and it looks like we used to do that in some very old\ntags), but there may be some possible downsides:\n\n 1. I'm not sure if anybody depends on the current format for\n scripting.\n\n 2. They can't be revised if we later fix up the Release Notes (e.g.,\n typo fixes, but also they were recently all retroactively brushed\n up to be renderable as asciidoc).\n\n 3. The resulting objects would be much larger (the v2.51.0 tag is 974\n bytes, but Documentation/RelNotes/2.51.0 is 14K, and some are even\n larger). Git may open them frequently to peel the tags, which may\n make some operations slower. Though it might be OK; we try to cache\n peeled values in packed-refs, and possibly the peeling code could\n learn to parse more progressively (e.g., grab the first 1K to see\n if we hit the end-of-header there).\n\nThose aren't necessarily show-stoppers, but just some top-of-the-head\nthoughts. Junio (the maintainer, who actually makes the tags) might have\nmore thoughts on why we used to do that sometimes and don't now.\n\n-Peff\n"},{"id":"526985","messageId":"xmqqy0q6rydz.fsf@gitster.g","threadId":"64182","inReplyTo":"20250922201403.GD2205919@coredump.intra.peff.net","subject":"Re: How do i get news of git releases","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-09-22T21:05:44Z","receivedAt":"2025-09-22T21:05:47Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jeff King writes:\n\n> The project doesn't use GitHub's Releases feature specifically, but I\n> think annotated tags that are pushed to the repo end up there, too. The\n> resulting feed entries are a little bare. Possibly they could be\n> populated with the release notes, but from the Git project's\n> perspective, the GitHub repo is really just a Git mirror. Presumably it\n> would require some scripting around GitHub's API for the tag pushes to\n> also create Release entries (and then probably somebody would want the\n> same for the GitLab mirror, and so on).\n>\n> I think it may also be a reasonable feature for git-scm.com to have its\n> own RSS feed. It already has to know about all of the releases (so it\n> can point to the most recent one, for example). Most of the development\n> for that site happens at https://github.com/git/git-scm.com. So if you\n> or anybody is interested in adding the feature, it would probably make\n> sense to start a discussion there.\n\nIt would give us a bit finer grained report to trigger updates to\nthe blob RelNotes symbolic link points at, if the rss geneators can\nmonitor such things.\n"},{"id":"526989","messageId":"xmqqtt0urxva.fsf@gitster.g","threadId":"64182","inReplyTo":"20250922203815.GA2264272@coredump.intra.peff.net","subject":"Re: How do i get news of git releases","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-09-22T21:16:57Z","receivedAt":"2025-09-22T21:16:59Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Jeff King writes:\n\n> Yes, they're already annotated tags. But they contain only the version\n> number and signature. I suppose they could include the whole set of\n> release notes (and it looks like we used to do that in some very old\n> tags),\n\nEh, which one? I do not recall ever doing so, but I may be\nmistaken.\n\n\"git show v0.99.1\" gives both tag object contents *and* the output\nfrom \"git show v0.99.1^0\" for the commit, so it is possible that I\nnever did so, but those who ask \"git show\" may get such an\nimpression?\n\n> but there may be some possible downsides:\n>\n> 1. I'm not sure if anybody depends on the current format for\n> scripting.\n>\n> 2. They can't be revised if we later fix up the Release Notes (e.g.,\n> typo fixes, but also they were recently all retroactively brushed\n> up to be renderable as asciidoc).\n>\n> 3. The resulting objects would be much larger (the v2.51.0 tag is 974\n> bytes, but Documentation/RelNotes/2.51.0 is 14K, and some are even\n> larger). Git may open them frequently to peel the tags, which may\n> make some operations slower. Though it might be OK; we try to cache\n> peeled values in packed-refs, and possibly the peeling code could\n> learn to parse more progressively (e.g., grab the first 1K to see\n> if we hit the end-of-header there).\n>\n> Those aren't necessarily show-stoppers, but just some top-of-the-head\n> thoughts. Junio (the maintainer, who actually makes the tags) might have\n> more thoughts on why we used to do that sometimes and don't now.\n\nI think #3 is a show-stopper.\n\nWe will keep the RelNotes file updated with every batch that updates\nthe 'master' front, so the contents of that imaginary tag that has\nthe copy of the release notes would become identical to the in-tree\nblob at the point of a release. There has to be a very good reason\nwhy it is beneficial to _duplicate_ the information, not the other\nway around to ask why we do not duplicate the information in\ndifferent places, I think.\n"},{"id":"526992","messageId":"20250922213558.GA2269472@coredump.intra.peff.net","threadId":"64182","inReplyTo":"xmqqtt0urxva.fsf@gitster.g","subject":"Re: How do i get news of git releases","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2025-09-22T21:35:58Z","receivedAt":"2025-09-22T21:35:59Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Mon, Sep 22, 2025 at 02:16:57PM -0700, Junio C Hamano wrote:\n\n> Jeff King writes:\n> \n> > Yes, they're already annotated tags. But they contain only the version\n> > number and signature. I suppose they could include the whole set of\n> > release notes (and it looks like we used to do that in some very old\n> > tags),\n> \n> Eh, which one? I do not recall ever doing so, but I may be\n> mistaken.\n> \n> \"git show v0.99.1\" gives both tag object contents *and* the output\n> from \"git show v0.99.1^0\" for the commit, so it is possible that I\n> never did so, but those who ask \"git show\" may get such an\n> impression?\n\nI looked at:\n\n git for-each-ref --format='%(objectsize) %(refname)' refs/tags |\n sort -n\n\nwhich shows a few bigger ones. v0.99.5 is the biggest, with what looks\nlike shortlog output plus some hand-written notes. Ditto v1.4.3.2.\nBut yeah, it is not very many.\n\n> > 3. The resulting objects would be much larger (the v2.51.0 tag is 974\n> > bytes, but Documentation/RelNotes/2.51.0 is 14K, and some are even\n> > larger). Git may open them frequently to peel the tags, which may\n> > make some operations slower. Though it might be OK; we try to cache\n> > peeled values in packed-refs, and possibly the peeling code could\n> > learn to parse more progressively (e.g., grab the first 1K to see\n> > if we hit the end-of-header there).\n> >\n> > Those aren't necessarily show-stoppers, but just some top-of-the-head\n> > thoughts. Junio (the maintainer, who actually makes the tags) might have\n> > more thoughts on why we used to do that sometimes and don't now.\n> \n> I think #3 is a show-stopper.\n> \n> We will keep the RelNotes file updated with every batch that updates\n> the 'master' front, so the contents of that imaginary tag that has\n> the copy of the release notes would become identical to the in-tree\n> blob at the point of a release. There has to be a very good reason\n> why it is beneficial to _duplicate_ the information, not the other\n> way around to ask why we do not duplicate the information in\n> different places, I think.\n\nYeah, I agree the duplication is kind of unseemly. The main reason, I\nthink, would be: some third-party tools may mine information out of the\ntag automatically, but do not know how to find Documentation/RelNotes.\nI'm assuming GitHub would do that for the releases page (but actually, I\ndo not know).\n\nIf we did care about populating their releases page with more info, I\nsuspect using their API to pass along the content would be a better\nsolution.\n\n-Peff\n"},{"id":"527038","messageId":"CAP8UFD2asXf_4_02khYRVWVQruBdvoMkZVE-6cVHttT9gHdWqw@mail.gmail.com","threadId":"64182","inReplyTo":"4ea9cb1e-4367-4926-a9ba-0680dd63e616@velocifyer.com","subject":"Re: How do i get news of git releases","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2025-09-23T09:43:39Z","receivedAt":"2025-09-23T09:43:52Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Mon, Sep 22, 2025 at 7:43 PM 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣\n wrote:\n>\n> How do i get changelogs for git in a convinent format (like email or RSS\n> or Atom)? I see that i can get changelogs in /Documentation/RelNotes/\n> but then i have to check the folder manually instead of it being in my\n> email and RSS and Atom client (Thunderbird).\n\nNot sure it is what you need, but just in case, there is:\n\nhttps://github.com/chriscool/getreleases\n\nthat we use to automatically generate release information that we\npublish in our Git Rev News newsletter:\n\nhttps://git.github.io/rev_news/archive/\n\nYou can use it like this:\n\n$ ./get_releases.py --get \"Git\" --exact --since 2025-07-24\nGetting releases for exactly \"Git\" since 2025-07-24\n\n> Requesting https://lore.kernel.org/git/?q=d%3A20250724..+%5BANNOUNCE%5D+Git\n+ Git [2.51.0](https://lore.kernel.org/git/xmqqikikk1hr.fsf@gitster.g/),\n[2.51.0-rc2](https://lore.kernel.org/git/xmqqh5ybcfwt.fsf@gitster.g/),\n[2.51.0-rc1](https://lore.kernel.org/git/xmqqikizoybn.fsf@gitster.g/),\n[2.51.0-rc0](https://lore.kernel.org/git/xmqqms8f5889.fsf@gitster.g/\n\nThe URL for each release points to the announcement email on the\nmailing list archive. That email contains the release notes.\n"},{"id":"527129","messageId":"b5867a92-c516-4a66-a108-8cabbc166336@velocifyer.com","threadId":"64182","inReplyTo":"CAP8UFD2asXf_4_02khYRVWVQruBdvoMkZVE-6cVHttT9gHdWqw@mail.gmail.com","subject":"Re: How do i get news of git releases","fromName":"𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣","fromEmail":"velocifyer@velocifyer.com","sentAt":"2025-09-23T19:41:55Z","receivedAt":"2025-09-23T19:42:08Z","isPatch":false,"sender":{"key":"velocifyer@velocifyer.com","avatar":null},"body":"> The URL for each release points to the announcement email on the\n> mailing list archive. That email contains the release notes.\nIf they already have the realease notes on the mailing list, why do they \nnot have a seprate \"git-announce\" mailing list with just the release \nnotes and other important announcements\n-- \nGeorge truly, 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣\nImprove your wifi reception for free \n\nThis email does not constitute a legally binding contract ‮\nRemember to reply all on mailing lists (this is here so i don't forget \nto use reply all)(If you are reading this i forgot to remove it)\n"},{"id":"527195","messageId":"CAP8UFD0t76v3XYgoLjZ-527EePQKihSNyA=AO0QjJHDy=u32JQ@mail.gmail.com","threadId":"64182","inReplyTo":"b5867a92-c516-4a66-a108-8cabbc166336@velocifyer.com","subject":"Re: How do i get news of git releases","fromName":"Christian Couder","fromEmail":"christian.couder@gmail.com","sentAt":"2025-09-24T08:38:17Z","receivedAt":"2025-09-24T08:38:30Z","isPatch":false,"sender":{"key":"christian.couder@gmail.com","avatar":"https://avatars.githubusercontent.com/u/208954?v=4"},"body":"On Tue, Sep 23, 2025 at 9:42 PM 𝕍𝕖𝕝𝕠𝕔𝕚𝕗𝕪𝕖𝕣\n wrote:\n>\n> > The URL for each release points to the announcement email on the\n> > mailing list archive. That email contains the release notes.\n\n> If they already have the realease notes on the mailing list, why do they\n> not have a seprate \"git-announce\" mailing list with just the release\n> notes and other important announcements\n\nWe try to keep everything on a single mailing list as much as possible\nto not split the community. Also what is important depends a lot on\nthe reader. For example Git for Windows or Git Rev News announcements\nmight be important for some but not for others. So many people would\nhave to sort things out anyway even if there were separate mailing\nlists.\n"},{"id":"527249","messageId":"xmqqcy7flm54.fsf@gitster.g","threadId":"64182","inReplyTo":"CAP8UFD0t76v3XYgoLjZ-527EePQKihSNyA=AO0QjJHDy=u32JQ@mail.gmail.com","subject":"Re: How do i get news of git releases","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2025-09-24T18:51:19Z","receivedAt":"2025-09-24T18:51:21Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Christian Couder writes:\n\n> On Tue, Sep 23, 2025 at 9:42 PM\n> wrote:\n>>\n>> > The URL for each release points to the announcement email on the\n>> > mailing list archive. That email contains the release notes.\n>\n>> If they already have the realease notes on the mailing list, why do they\n>> not have a seprate \"git-announce\" mailing list with just the release\n>> notes and other important announcements\n>\n> We try to keep everything on a single mailing list as much as possible\n> to not split the community.\n\nI do not see how the presence of an \"announce-only\" list would\nfracture the community. You could make such a list strictly\nread-only for participants (i.e. only the list owners can send\nthings out, responses may be routed to those on whose behalf the\nmessage was sent to the list, just to /dev/null, or perhaps to the\nmain list) for make it even clear that the secondary list is for\nannounce-only and any discussion about the items announced would\nstill happen on the main list.\n\nIt does take resources and coordination. It won't happen without\nanybody spending an extra effort.\n\nBecause those who would be writing the announce material for such a\nsecondary list are making enough efforts to help this community\nthrive already, I do not particularly see the initial \"why not a\nseparate announce list\" question a very productive thing to think\nabout or respond to. Unless the requestor is proposing to help such\nan effort on continuous basis, that is.\n\n> Also what is important depends a lot on the reader. For example\n> Git for Windows or Git Rev News announcements might be important\n> for some but not for others. So many people would have to sort\n> things out anyway even if there were separate mailing lists.\n\nThat's very true.\n"}]}