I have a merge commit to devel/c++-coroutines, which is intended to refect
the state at the point of commit to trunk.
However, I cannot push that commit because:
remote: *** This update introduces too many new commits (284), which would
remote: *** trigger as many emails, exceeding the current limit (100).
remote: *** Contact your repository adminstrator if you really meant
remote: *** to generate this many commit emails.
remote: error: hook declined to update refs/heads/devel/c++-coroutines
To git+ssh://gcc.gnu.org/git/gcc.git
! [remote rejected] devel/c++-coroutines -> devel/c++-coroutines (hook
declined)
in fact, I usually merged trunk into the branch weekly - this one got
slightly delayed because it was intended to be the final one.
284 isn’t a lot of trunk commits for an interval between merges into a
devel branch, so this seems likely to fire quite often.
——
So I know that the policy is under review (and agree, from my PoV, that
something that represents these in a similar way to the SVN single mail
containing all the changes is probably optimum).
However, right now I’m stuck - and really want to get a short-term
resolution so that i can complete the merge of coroutines onto trunk.
I guess I could do a squashed merge from trunk - presumably, that would
only generate 1 email?
cheers
Iain
