From 5e4e85f30efa3b4585c6f388b1f128c1c29b7c94 Mon Sep 17 00:00:00 2001 From: You-Sheng Yang Date: Tue, 7 Oct 2025 14:39:46 +0800 Subject: [PATCH 1/3] how-to: source-code: sending-patches: remove prompt marks Per Canonical Documentation Style Guide (https://docs.ubuntu.com/styleguide/en/#code-examples-in-documentation), remove shell prompt marks. Signed-off-by: You-Sheng Yang --- docs/how-to/source-code/send-patches.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/how-to/source-code/send-patches.rst b/docs/how-to/source-code/send-patches.rst index 9721c9a..768b342 100644 --- a/docs/how-to/source-code/send-patches.rst +++ b/docs/how-to/source-code/send-patches.rst @@ -20,7 +20,7 @@ Specify the targeted series with the ``--subject-prefix`` option: .. code-block:: shell - $ git send-email --subject-prefix="SRU][o/n/j:linux-azure][PATCH" ... + git send-email --subject-prefix="SRU][o/n/j:linux-azure][PATCH" ... The tags used in this example show that this patch set is targeting the following kernels for an SRU update: *oracular*, *noble*, and @@ -34,7 +34,7 @@ patchset that fixes some issues, you can use the ``-v,--reroll-count`` option: .. code-block:: shell - $ git send-email --subject-prefix=... -v 2 + git send-email --subject-prefix=... -v 2 This will generate ``[PATCH v2]`` instead of just ``[PATCH]`` to indicate that this is a new revision of a patchset. From c99e08ea958378b090e91bd4c425af9d665bceb5 Mon Sep 17 00:00:00 2001 From: You-Sheng Yang Date: Tue, 7 Oct 2025 14:58:21 +0800 Subject: [PATCH 2/3] how-to: source-code: sending-patches: add the usage of --identity Signed-off-by: You-Sheng Yang --- docs/how-to/source-code/send-patches.rst | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/docs/how-to/source-code/send-patches.rst b/docs/how-to/source-code/send-patches.rst index 768b342..99b57dd 100644 --- a/docs/how-to/source-code/send-patches.rst +++ b/docs/how-to/source-code/send-patches.rst @@ -12,6 +12,18 @@ send-email`` command. ``git-send-email`` but ``git-format-patch`` instead. They however work the same. +One may want to create a specific identity for keeping common settings when +sending kernel patches. The commonly used settings are: + +.. code-block:: shell + + git config set sendemail.ubuntu-kernel.chainReplyTo false + git config set sendemail.ubuntu-kernel.suppresscc true + git config set sendemail.ubuntu-kernel.thread true + + # And then include these settings with `--identity=ubuntu-kernel` + git send-email --identity=ubuntu-kernel ... + Specify series ============== From ea1d2c2e6cb8d40bd9e6bf0be72cd4af6d39b0de Mon Sep 17 00:00:00 2001 From: AnneCYH Date: Thu, 9 Oct 2025 10:50:15 +0800 Subject: [PATCH 3/3] Update send-patches.rst Signed-off-by: AnneCYH --- docs/how-to/source-code/send-patches.rst | 27 ++++++++++++------------ 1 file changed, 14 insertions(+), 13 deletions(-) diff --git a/docs/how-to/source-code/send-patches.rst b/docs/how-to/source-code/send-patches.rst index 99b57dd..030827e 100644 --- a/docs/how-to/source-code/send-patches.rst +++ b/docs/how-to/source-code/send-patches.rst @@ -12,7 +12,7 @@ send-email`` command. ``git-send-email`` but ``git-format-patch`` instead. They however work the same. -One may want to create a specific identity for keeping common settings when +You may want to create a specific identity for keeping common settings when sending kernel patches. The commonly used settings are: .. code-block:: shell @@ -32,17 +32,17 @@ Specify the targeted series with the ``--subject-prefix`` option: .. code-block:: shell - git send-email --subject-prefix="SRU][o/n/j:linux-azure][PATCH" ... + git send-email --subject-prefix="SRU][O/N/J:linux-azure][PATCH" ... -The tags used in this example show that this patch set is targeting the +The tags used in this example show that this patchset is targeting the following kernels for an SRU update: *oracular*, *noble*, and *jammy:linux-azure*. Send a new version of a patchset ================================ -Mistakes happens, we are all humans. If you want to send a new version of your -patchset that fixes some issues, you can use the ``-v,--reroll-count`` option: +Mistakes happen; we are all human. If you want to send a new version of your +patchset that fixes some issues, you can use the ``-v, --reroll-count`` option: .. code-block:: shell @@ -52,14 +52,15 @@ This will generate ``[PATCH v2]`` instead of just ``[PATCH]`` to indicate that this is a new revision of a patchset. You should first make sure that your original patchset was rejected by having a -NAK/NACK in its thread. You can reply to this email saying that you will send a -new version of the patchset. If you found out a mistake you made, you can NAK -and say that you will send a new version in the same email. +NAK/NACK in its thread. You can reply to the email saying that you will send a +new version of the patchset. -In the cover letter of the new patchset, you should describe what was changed -compared to the previous submitted version. +If you found a mistake you made, you can NAK and say that you will send a new +version in the same email. -See also -======== +In the cover letter of the new patchset, describe what was changed compared +to the previous submitted version. -- (Reference) :ref:`ubuntu-patches-acceptance-criteria` +.. seealso:: + + - (Reference) :ref:`ubuntu-patches-acceptance-criteria`