Hi, On Mon, Jun 15 2020, Segher Boessenkool wrote: > Hi! > [...] > 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?
while I tend to agree that sending emails about commits to user branches is not a good idea, I also believe that you should (almost?) never rebase a public branch. Certainly not if you expect anyone else to fetch it or - god forbid - base some of their commits on it, as opposed to just reading it through the web interface. I'd suggest appending a date to the namer of the branch and thus always publish a new branch, making it clear that its history is different. Martin
