Let's see if watching the git repo (and filtering if necessary) covers this use case before we build more custom infrastructure. On Wed, Sep 7, 2016 at 2:46 PM, Emanuel Barry <vgr255@live.ca> wrote:
Fair enough. I never really bothered to set up any complicated design to get commits, and my emails all get automatically sorted into folders so it doesn’t matter which list it goes to. Although now that you mention it, I could simply subscribe to the GitHub repos and get the notifications for free :)
-Emanuel
From: Brett Cannon [mailto:brett@python.org] Sent: Wednesday, September 07, 2016 5:40 PM To: Emanuel Barry; python-dev@python.org Subject: Re: [Python-Dev] Commits to migrated repos no longer sent to Python-checkins
On Wed, 7 Sep 2016 at 14:24 Emanuel Barry <vgr255@live.ca> wrote:
The repos which used to send to Python-checkins no longer do so since their respective migrations (devguide, peps). I don't know who's responsible for that, so I figured I'd post here.
If people want those back on then that could be arranged. I'm not sure, though, if it still makes sense having emails for every commit from three separate repositories going to the same mailing list.
You can follow the commits through an atom feed, e.g https://github.com/python/peps/commits.atom. That means you could use something like IFTTT on your own to send you an email for each commit so you can track only the repositories you care about. That makes me think that it's worth even less for peps since those all have to be posted here anyway and the devguide doesn't affect people's future production deployments.
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/guido%40python.org
-- --Guido van Rossum (python.org/~guido)