Hi Mark, Mark H Weaver <m...@netris.org> writes:
> Tomas Volf <~@wolfsden.cz> writes: >> Taking into account that it includes also the comments and >> such, that Guix repository is pretty active and that there are only 30 >> entries in the feed, I would probably need to check close to every >> second to make sure I do not miss anything. Which seems excessive. > > Occasionally, large numbers of commits are pushed in a single operation, > possibly more than 30. Even if you check the RSS feed every second, I'm > not sure that would ensure that nothing was missed. Did you see my reply to Tomas earlier? Forgejo/Codeberg provides a RSS feed exactly made for the purpose of tracking commits to a branch; you can test it for the master branch in Guix using the following url: https://codeberg.org/guix/guix/rss/branch/master I've been using it, and it works well. I don't think you can 'loose' notifications with RSS (that seemed to be a concern). It doesn't show the diff in the messages but includes an URL to visit that does. > On the other hand, the most reliable method by far is to periodically > fetch from the git repository itself and look through the new commits > locally on your own machine. If anyone cares enough, it wouldn't be > hard to write a simple script to generate emails similar to the ones > that are currently being sent out to guix-commits. > > What do you think? I think the per-branch RSS feed should cover the main use case (keeping an eye as to what is being pushed to the repo) while being lighter on resources than emails containing the whole commit data. In light of this, I think it'd make sense to sunset the guix-commits mailing list. Do we have consensus? -- Thanks, Maxim
