Hello Tom, Thank you! It seems the only reasonable solution. I'm just slightly worried about commits being made non-atomic :(
On Tue, Sep 28, 2021 at 12:06 AM Tom Rini <tr...@konsulko.com> wrote: > > On Mon, Sep 27, 2021 at 05:58:08PM +0300, Oleksandr Suvorov wrote: > > > Dear community, > > > > This weekend I tried to post (using patman) a patch set that should > > have been sent to 120 recipients (a lot of files were changed). > > > > I've got an error from the Gmail SMTP server: > > 4.5.3 Your message has too many recipients. For more information regarding > > 4.5.3 Google's sending limits, please visit: > > 4.5.3 https://support.google.com/mail/?p=TooManyRecipientsError > > e1sm1539543ljp.114 - gsmtp > > > > The doc says there is a limit for recipients - 100 per message. All my > > emails are hosted by Gmail/G-suit. I think I'm not the first who faced > > such an issue. > > Could you share your tricks or best practices on how to post patch > > sets with more than 100 recipients without changing an e-mail > > provider? > > > > Thanks in advance for your help! > > Honestly, that probably means the patch needs to be split up more. Per > SoC / SoC family perhaps. > > -- > Tom -- Best regards, Oleksandr Suvorov Software Engineer T: +380 63 8489656 E: oleksandr.suvo...@foundries.io W: www.foundries.io