docs/devel/submitting-a-patch.rst

232 to another list.) ``git send-email`` (`step-by-step setup guide
233 <https://git-send-email.io/>`__ and `hints and tips
243 If you already configured git send-email, you can simply use `git-publish
244 <https://github.com/stefanha/git-publish>`__ to send series.
252     $ git publish # will send a v2
265 If you cannot send patch emails
268 In rare cases it may not be possible to send properly formatted patch
269 emails. You can use `sourcehut <https://sourcehut.org/>`__ to send your
277 #. Send your patches to the QEMU mailing list using the web-based
278    ``git-send-email`` UI at https://git.sr.ht/~USERNAME/qemu/send-email
288 Send patches both to the mailing list and CC the maintainer(s) of the
303 Do not send as an attachment
306 Send patches inline so they are easy to reply to with review comments.
318 using ``git send-email`` to mail the files to the mailing list. (We
319 recommend `git send-email <http://git-scm.com/docs/git-send-email>`__
321 messing up whitespace. Some distributions do not include send-email in a
326 patches do not need a cover letter (but if you do send a cover letter,
457 respond to these, and then send a second version of your patches with
493 identify which patches are relevant. Send the new version as a complete
511 send-email <http://git-scm.com/docs/git-send-email>`__ both understand
512 the ``-v2`` option to make this easier. Send each new revision as a new
587 send you an automated mail if it detected a problem with your patch.
590 area of code will send notification to the list that they are including
594 need to send a pull request unless you have contributed enough patches