> rather that a separate mailing list, are there internal aliases or lists

corresponding to the project group admins or the bug tracker global list?

There are not.

We could hard code in a list of addresses.  And it is not difficult to edit those later.

But mailing lists are pretty much without any cost incrementally.  We have some 1500+ mailing lists already and incrementally adding another one is not a burden.  Therefore it's the thing we reach for most often.

Normally we don't block access to the CVS repository as it is often needed again.  Often people find that they did a conversion with an error and need to do it again.  Sometimes people have need to look back into the previous repository.

If you wish to redirect people who checkout the cvs repository then I suggest deleting all of the files from there and committing only a README file that redirects them.  That's best.  Because then you can redirect them from the old repository to the new repository.

Normally the commits or diffs mailing list would contain the output of a hook which emails the commitdiff of the commit.  It is the result of installing a hook script.  As to what the script might do the script might do anything that one wants it to do.  And therefore it's a little hard to answer the question of what commit notification email might be sent because it might be anything that one could program and that could be almost anything.

I might suggest the emacs diffs hook using the git_multimail program as being a typical example.  It's a 3rd party project.  And there are other commitdiff notification programs and configurations available too.

https://lists.gnu.org/archive/html/emacs-diffs/2024-02/threads.html

You said you looked at other commit notification lists and therefore I am sure you noticed that there are different notification styles in use.  If you liked one of them more than another we would happily clone the configuration of that one for you.