On June 15, 2020 7:19:13 PM GMT+02:00, Joseph Myers <jos...@codesourcery.com> wrote: >On Mon, 15 Jun 2020, Segher Boessenkool wrote: > >> It should never send email for things that are on master (or any >release >> branch) already. > >https://github.com/AdaCore/git-hooks/issues/9 > >https://github.com/AdaCore/git-hooks/pull/12 is marked "Approved". It >certainly has fixes for some of the issues reported in the GCC context, > >but I'm not sure if it includes a fix for that particular one. And >once >"Approved" has turned into actually present in master, the upstream >changes will need merging into the version used by GCC (replacing local > >changes where the features those implement have been implemented more >generally upstream). > >> It should never send email for user branches *at all*. > >I think sending email for all branches showing the development taking >place there (as opposed to commits that are already in the repository >and >are just being added to another ref) is entirely appropriate. > >I don't know if deleting and then recreating a user branch (in separate > >pushes) avoids the limit (and the excess mails) in the case where a >user >branch is being rebased, but I expect it should.
Can you document this (and how to do it) in git.html?
