The webkit-changes mailing lists was very useful in a number of scenarios. The same things can be achieved in other ways with git, but less efficiently or elegantly. - look at changes as they are being landed; - search for changes by keyword using mail client; - efficiently step through changes in an identified regression or progression range. Having SVN revisions and location of changes in titles was particularly useful. E.g. "[295779] trunk/Source/WebCore/accessibility" was the last of those. With GitHub not showing identifiers prominently, email archive could be part of the solution (although we should also have a history view on commits.webkit.org).
<rdar://problem/98466544>
Github does appear to offer email notification about commits. https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/about-email-notifications-for-pushes-to-your-repository
(In reply to Brandon from comment #2) > Github does appear to offer email notification about commits. > > https://docs.github.com/en/repositories/managing-your-repositorys-settings- > and-features/managing-repository-settings/about-email-notifications-for- > pushes-to-your-repository That is a little light on details, specifically in regard to whether notifications can include the entire content of the change (rather than just a commit message and a link to a website).
We've enabled GitHub emails for now. The first few went in batches, but it should be real time now. Still need a better solution: - need identifier in the title, not a hash; - need full content (up to a certain limit); - don't need "[WebKit/WebKit]" in the title.