docs/devel/submitting-a-patch.rst

66 Base patches against current git master
75 not yet part of the git master branch. To aid continuous integration
90 `git bisect <http://git-scm.com/docs/git-bisect>`__ without hitting
109 from the raw code motion. Use a one-time setup of ``git config
110 diff.renames true;`` ``git config diff.algorithm patience`` (refer to
111 `git-config <http://git-scm.com/docs/git-config>`__). The 'diff.renames'
123     git format-patch --stdout -1 > patch;
153 QEMU follows the usual standard for git commit messages: the first line
157 not end in a dot. Look at ``git shortlog -30`` for an idea of sample
161 commit message (so that the text still shows up nicely with "git show"
192 "Tested-by:", "Acked-by:", "Reported-by:", "Suggested-by:".  See ``git
232 to another list.) ``git send-email`` (`step-by-step setup guide
233 <https://git-send-email.io/>`__ and `hints and tips
240 Use git-publish
243 If you already configured git send-email, you can simply use `git-publish
244 <https://github.com/stefanha/git-publish>`__ to send series.
248     $ git checkout master -b my-feature
250     $ git publish
252     $ git publish # will send a v2
254 Each time you post a series, git-publish will create a local tag with the format
257 When sending patch emails, 'git publish' will consult the output of
275 #. Publish your git branch using **git push git@git.sr.ht:~USERNAME/qemu
278    ``git-send-email`` UI at https://git.sr.ht/~USERNAME/qemu/send-email
281 <https://man.sr.ht/git.sr.ht/#sending-patches-upstream>`__.
297 In fact, you can automate this, via a one-time setup of ``git config
299 `git-config <http://git-scm.com/docs/git-config>`__.)
311 Use ``git format-patch``
315 `git format-patch <http://git-scm.com/docs/git-format-patch>`__ will
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>`__
322 default install of git; you may need to download additional packages,
323 such as 'git-email' on Fedora-based systems.) Patch series need a cover
337 emails using ``git format-patch --no-binary`` and include a link to a
338 git repository to fetch the original commit.
360 one-time setup of ``git config format.coverletter auto`` (refer to
361 `git-config <http://git-scm.com/docs/git-config>`__) will generate the
380 For example, "[PATCH RFC v2]". ``git format-patch --subject-prefix=RFC``
509 track versions of different patches in the series separately.  `git
510 format-patch <http://git-scm.com/docs/git-format-patch>`__ and `git
511 send-email <http://git-scm.com/docs/git-send-email>`__ both understand
524 formatted as a git patch, the commit message is the part above the ``---``
525 line, and this will go into the git changelog when the patch is
528 back to look at this commit in git in six months' time. The part below
529 the ``---`` line and above the patch proper (git format-patch puts the
532 summary belongs. The `git-publish
533 <https://github.com/stefanha/git-publish>`__ script can help with
534 tracking a good summary across versions. Also, the `git-backport-diff
535 <https://github.com/codyprime/git-scripts>`__ script can help focus
602 patch first had a positive review to when it finally lands in qemu.git;