On June 15, 2020 6:05:26 PM GMT+02:00, Segher Boessenkool <seg...@kernel.crashing.org> wrote: >Hi! > >$ git push -n fsf >To git+ssh://gcc.gnu.org/git/gcc.git > + 1db88c6...71e5e35 cc0 -> refs/users/segher/heads/cc0 (forced update) > >$ git push fsf >Counting objects: 664, done. >Delta compression using up to 64 threads. >Compressing objects: 100% (239/239), done. >Writing objects: 100% (504/504), 87.72 KiB | 0 bytes/s, done. >Total 504 (delta 434), reused 321 (delta 265) >remote: Resolving deltas: 100% (434/434), completed with 159 local >objects. >remote: *** !!! WARNING: This is *NOT* a fast-forward update. >remote: *** !!! WARNING: You may have removed some important commits. >remote: *** This update introduces too many new commits (2898), which >would >remote: *** trigger as many emails, exceeding the current limit (1000). >remote: *** Contact your repository adminstrator if you really meant >remote: *** to generate this many commit emails. >remote: error: hook declined to update refs/users/segher/heads/cc0 >To git+ssh://gcc.gnu.org/git/gcc.git > ! [remote rejected] cc0 -> refs/users/segher/heads/cc0 (hook declined) >error: failed to push some refs to 'git+ssh://gcc.gnu.org/git/gcc.git' > >What. > >Of course it is not a fast-forward. I rebase the branches I publish, >what is the point of publishing them otherwise? This is so that people >can see the stuff that will make its way into master *later*. > >The number of new commits is nonsense (it is just 13), and the number >of >emails that triggers should be 0. > >Please fix? Or, what else is wrong?
The number of commits is. From merges I suppose. Richard. > > >Segher
