Hi Ian, > As I noted, 100 commits to master is a small number, so I expect this problem > to fire almost every time someone does a merge of master to a devel or user > branch (unless they have the habit of doing that almost daily, which I doubt > for > most).
The main goal of the limit is really to avoid accidents where someone pushes something he shouldn't or something he didn't realize would push so many commits. If the GCC repository is such that merges of 100 commits or more is going to be, if not routine, at least to be expected, then perhaps increasing the limit would make sense. What I would do is wait a bit and see. This may become moot soon, depending on the direction that we want to take for vendor/user branches with respect to emails. I'm still trying to think this over... -- Joel
