Hi Jacopo, On Wed, Jun 24, 2020 at 09:47:49AM +0200, Jacopo Mondi wrote: > On Tue, Jun 23, 2020 at 02:17:49PM +0200, Eugeniu Rosca wrote: > > Hi Jacopo, > > > > On Tue, Jun 23, 2020 at 12:49:03PM +0200, Jacopo Mondi wrote: > > > On Tue, Jun 23, 2020 at 12:30:02PM +0200, Eugeniu Rosca wrote: > > > > On Mon, Jun 22, 2020 at 07:26:14PM +0200, Jacopo Mondi wrote: > > > > > My ISP has rejected the rest of the series: too many emails :( > > > > > Has it ever happened to anyone else ? How did you solved this ? > > > > > > > > I guess leaving 5-10 seconds between sending individual patches should > > > > overcome this? I wonder if git provides a built-in command for that? > > > > > > > > > > git send-email does provide the --batch-size --relogin-delay options, > > > as Ezequiel suggested me in #v4l. > > > > > > I tried re-sending with a 10 email batch and a 5 seconds delay but I > > > got the same failure. I was not able to find any description of the > > > email number limits for the SMTP server I'm using, so I could only go > > > and try. I think the extensive CC list of this series which I got from > > > Roman's series plays a role, so I can't try just by sending to > > > myself... I wonder if I should send the series in chunks, the first 10 > > > patches went out (2 times '-.- ) already... > > > > Any time you send a new batch, please call 'git send-email' with > > '--in-reply-to=<cover-letter-id>' to allow LKML front-ends identify > > the patches as belonging to one topic and make it less of a pain > > for people to go through these discussions later on. > > Thanks for the suggestion, I hope I got it right ;) The series has now > been resent. That's right. I now see all 25 patches appearing under the same umbrella of https://patchwork.linuxtv.org/cover/64822/ (via "Related"), even if the last 15 have been sent out at a later point in time. -- Best regards, Eugeniu Rosca
