On Tue, May 19, 2026 at 04:09:32PM +0800, SignKirigami wrote: > Please disregard my previous patch series[1][2][3][4][5][6]. > This was my first time using git send-email and my provider > messed up the threads (the cover letter also accidentally > reused a previous Message-ID, causing it to be grouped into > the wrong thread[7]).
FWIW, personally I can recommend using the "git-publish" tool for sending patch series as it makes it (mostly) foolproof. Assuming you've got your work on a branch and keep using the same branch across multiple postings of a piece of work, then running 'git-publish' with no arguments will "do the right thing(tm)", includign: * Format a mail for every patch on that branch vs master * Add a cover letter automatically if there are 2+ patches * Use MAINTAINERS to automatically CC (mostly) the right people * Keep track of patch versions, incrementing after each posting * Remember the cover letter text across each posting * Send to qemu-devel by default The only config task for git-publish is to have the global git "sendemail.smtpserver" option set, which you'll have already done for git send-email. There is more guidance on submitting patches at: https://www.qemu.org/docs/master/devel/submitting-a-patch.html#submitting-your-patches > I sincerely apologize for the noise and confusion. No problem. With regards, Daniel -- |: https://berrange.com ~~ https://hachyderm.io/@berrange :| |: https://libvirt.org ~~ https://entangle-photo.org :| |: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
