On Mon, Jun 15, 2020 at 06:41:02PM +0200, Andreas Schwab wrote: > On Jun 15 2020, Segher Boessenkool wrote: > > > On Mon, Jun 15, 2020 at 06:28:39PM +0200, Richard Biener wrote: > >> On June 15, 2020 6:05:26 PM GMT+02:00, Segher Boessenkool > >> <seg...@kernel.crashing.org> wrote: > >> >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. > > > > It is just 13 new commits. It rebased though. There are no merges. > > What does git rev-list 1db88c6...71e5e35 | wc -l give?
A lot, of course, all on master already (I hadn't rebased this branch for quite a while, it waited for stage 1). (2911 in fact). It should never send email for things that are on master (or any release branch) already. It should never send email for user branches *at all*. User branches are *allowed* to rebase. And that is the only sane development model anyway, IMNSHO. The mail script should just ignore all user branches, and this script shouldn't do these tests for user branches. Segher
