[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[PATCH v2 2/6] docs/devel: add git-publish for patch submitting
From: |
Pierrick Bouvier |
Subject: |
[PATCH v2 2/6] docs/devel: add git-publish for patch submitting |
Date: |
Thu, 5 Dec 2024 14:22:37 -0800 |
Signed-off-by: Pierrick Bouvier <pierrick.bouvier@linaro.org>
---
docs/devel/submitting-a-patch.rst | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/docs/devel/submitting-a-patch.rst
b/docs/devel/submitting-a-patch.rst
index 03b2ac298aa..f8b7fc59544 100644
--- a/docs/devel/submitting-a-patch.rst
+++ b/docs/devel/submitting-a-patch.rst
@@ -235,6 +235,25 @@ 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.
+
.. _if_you_cannot_send_patch_emails:
If you cannot send patch emails
--
2.39.5
- [PATCH v2 0/6] Enhance documentation for new developers, Pierrick Bouvier, 2024/12/05
- [PATCH v2 4/6] docs/devel: add information on how to setup build environments, Pierrick Bouvier, 2024/12/05
- [PATCH v2 3/6] docs/devel: add b4 for patch retrieval, Pierrick Bouvier, 2024/12/05
- [PATCH v2 5/6] docs: add a codebase section, Pierrick Bouvier, 2024/12/05
- [PATCH v2 6/6] docs: add a glossary, Pierrick Bouvier, 2024/12/05