On Mon, Jun 15, 2020 at 10:43 AM Segher Boessenkool <seg...@kernel.crashing.org> wrote: > > Hi Joseph, > > Thanks, good to hear things will get better. > > On Mon, Jun 15, 2020 at 05:19:13PM +0000, Joseph Myers wrote: > > > It should never send email for user branches *at all*. > > > > I think sending email for all branches showing the development taking > > place there (as opposed to commits that are already in the repository and > > are just being added to another ref) is entirely appropriate. > > Not for these branches. All my user branches rebase. All diffs you mail > have to be three-way diffs, and even then they won't be super useful > (mostly showing conflict resolutions, and the few that are not are patch > series refactorings, and much much fewer you finally get the actual > patches). > > This shouldn't be archived at all, either, btw, IMNSHO; another reason > why it should not be sent to a mailing list. > > > I don't know if deleting and then recreating a user branch (in separate > > pushes) avoids the limit (and the excess mails) in the case where a user > > branch is being rebased, but I expect it should. > > I suspect that will work fine -- pushing the branch originally didn't > cause over a million emails, either. But that is much less convenient > and MUCH more error-prone than just allowing all rebases on user > branches in the first place -- and in fact it *does* seem to allow that, > it's just some "let's send a gazillion emails" script that is > misbehaving. >
These are all the reasons why I don't use GCC repo for my personal branches. -- H.J.
