Ezio Melotti

I added a comment on #6 with more information. In particular it would be useful to have a replacement for the weekly summary report mails. The dashboard and stats are...

This link has some stats: https://www.repotrends.com/python/cpython

Those refs were already broken since they mapped to hg.python.org, which hasn't been accessible in a while, so I didn't port them.

The rXXXXX revisions were updated in bpo to point to hg.python.org/lookup, so that e.g. r72662 linked to https://hg.python.org/lookup/r72662. Then the lookup script was supposed to find the hg changeset equivalent...

I found two files used by the lookup script: * [hglookup.py](https://github.com/python/psf-salt/blob/main/salt/hg/files/hg/src/hglookup.py) is the script itself * [hg_commits.json](https://github.com/python/psf-salt/blob/main/salt/hg/files/hg/src/hg_commits.json) is a flat list of HG commits There doesn't seem to be any...

It seems like `GH-*` were interpreted as issue number and converted automatically to the new migrated issue during the transfer. This automatic conversion was supposed to be disabled during the...

> i don't understand how GH-32112 was transformed to #76293 which is an unrelated issue (not a PR) During the transfer, https://bugs.python.org/issue32112 was transferred to https://github.com/python/cpython/issues/76293. The transfer tool thought...

Since this happened at transfer time, one of the test repos that I kept around might still have the correct references and it might be used to fix the links....

I don't have a number, and when we discussed different options to edit the messages after the fact and they all changed the "last updated" field (technically GitHub could rewrite...

A few things that might help you: * the migration happened in two stages: the import from bpo to a new GitHub repo, and the transfer from that repo to...