On Thu, Apr 06, 2023 at 05:19:24PM +0800, WANG Xuerui wrote: > Hi, > > On 2023/4/6 16:36, Xiaotian Wu wrote: > > I used "git send-email" to send patches #0 to #9, but after #6 patch > > was sent, the mail server told me: "too many commands", so I sent it > > again, the error remained. > > > > In the end, I sent #7 #8 #9 patches with "git send-email", so they are > > outside the thread.
OK, this explains everything. Thanks for the info. In the future in similar situations you can use "git send-email" "--in-reply-to" and "--no-thread" options to send the rest of patches as a reply to the #0 email. Simply look for "Message-ID:" header in the #0 email and copy its value to the "--in-reply-to" argument, e.g.: git send-email --in-reply-to '<ABC>' --no-thread ... > > So, what should I do now? Try resending or just reply to the current > > email? > As you're expected to add some commit messages before Daniel can start to > review anyway, I think you may as well do that and send v14 as a new series > afterwards. No need to resend v13 again. As Xuerui said, you do not need to send the v13 again. Just send v14 when you are ready. Thanks, Daniel _______________________________________________ Grub-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/grub-devel
