Gilles Grimaud <[email protected]> writes: > Hi Peter, > > Thanks for pointing this out, and sorry for breaking the series > threading. > > My university SMTP relay enforces a limit of 100 envelope recipients per > hour. Since each patch was sent to the QEMU lists and to the recipients > selected by scripts/get_maintainer.pl, the 37-message series reached that > limit partway through the submission. The relay then blocked further > messages as suspected bulk mail, and I cannot change that policy. > > I therefore resumed the series in two later git-send-email invocations. I > passed the original cover letter Message-ID with --in-reply-to, but I had > misunderstood how git-send-email threads a partial series: the first patch > of each resumed invocation became the parent of the remaining patches in > that batch. This produced the groups 17-30 and 31-36 seen in the archive > and prevented Patchew from recognizing the complete series. > > This was my mistake. I think I can avoid it for the next patch series by > using the appropriate git-send-email options to spread the messages over > time. > > I will also keep subsequent review discussions on the mailing list. My > earlier private reply was a mistake; I was trying to avoid triggering the > same SMTP restrictions, but review discussion should remain public.
If you are having issues with your university gateway you might want to consider using b4's web endpoint: https://b4.docs.kernel.org/en/latest/contributor/send.html of course you will have to manage your patch series with b4 to do that. I think you can set up via Source Hut's send-email web form: https://qemu.readthedocs.io/en/master/devel/submitting-a-patch.html#submitting-your-patches > > Thanks, > Gilles -- Alex Bennée Virtualisation Tech Lead @ Linaro
