Separate commit mailing lists for trunk/branches possible?

[Joseph Myers]

On Fri, 17 Jul 2020, Maciej W. Rozycki wrote:

>  Would it be reasonable to have the mailing list split into more than one, 
> that is at least the original covering the trunk, and then one or more for 
> branches?

https://github.com/AdaCore/git-hooks/issues/10 is the issue for that 
feature - implemented in the latest upstream version, but since merging 
upstream with our local changes and testing a merge will be a large amount 
of work, it seems sensible to wait for the other issues to be fixed first 
(and probably for the copy of the hooks shared by binutils-gdb, glibc etc. 
to be updated along with configuration for those repositories, first, 
since that has many fewer local changes and eventually it would be good 
for GCC to share that copy as well).  In particular, 
https://github.com/AdaCore/git-hooks/issues/9 is the issue regarding mails 
for commits that are already in the repository.

-- 
Joseph S. Myers
joseph@codesourcery.com