SYS-OSS/FRET-qemu
4
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

docs/devel: add git-publish for patch submitting

Browse Source 
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
Message-Id: <20241209183104.365796-3-pierrick.bouvier@linaro.org>
Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
Message-Id: <20250116160306.1709518-33-alex.bennee@linaro.org>
This commit is contained in:
Pierrick Bouvier 2025-01-16 16:03:01 +00:00 committed by Alex Bennée
parent 7b2c98854c
commit f4ac443efd
1 changed files with 25 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
docs/devel/submitting-a-patch.rst
View File

@ -235,6 +235,31 @@ to another list.) ``git send-email`` (`step-by-step setup guide
works best for delivering the patch without mangling it, but
attachments can be used as a last resort on a first-time submission.
.. _use_git_publish:
Use git-publish
~~~~~~~~~~~~~~~
If you already configured git send-email, you can simply use `git-publish
<https://github.com/stefanha/git-publish>`__ to send series.
::
$ git checkout master -b my-feature
$ # work on new commits, add your 'Signed-off-by' lines to each
$ git publish
$ ... more work, rebase on master, ...
$ git publish # will send a v2
Each time you post a series, git-publish will create a local tag with the format
``<branchname>-v<version>`` to record the patch series.
When sending patch emails, 'git publish' will consult the output of
'scripts/get_maintainers.pl' and automatically CC anyone listed as maintainers
of the affected code. Generally you should accept the suggested CC list, but
there may sometimes be scenarios where it is appropriate to cut it down (eg on
certain large tree-wide cleanups), or augment it with other interested people.
.. _if_you_cannot_send_patch_emails:
If you cannot send patch emails