summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMeh Mbeh Ida Delphine <idadelm@gmail.com>2021-03-16 19:30:59 +0100
committerGedare Bloom <gedare@rtems.org>2021-03-16 13:06:30 -0600
commita4755f6ee551b0175d287d605c33f99fa2cef614 (patch)
tree4d3a29d0c7ce9907acaf02b21f6273ca65ba2f8c
parentuser/bsps: Mention fixed console baud rate for zynq (diff)
downloadrtems-docs-a4755f6ee551b0175d287d605c33f99fa2cef614.tar.bz2
eng/vc-users: Set up patch message with repo name
Added instructions on how to set up a patch message with a repo name. Author: Meh Mbeh Ida Delphine <idadelm@gmail.com> Date: Tue Mar 16 19:11:23 2021 +0100
-rw-r--r--eng/vc-users.rst8
1 files changed, 8 insertions, 0 deletions
diff --git a/eng/vc-users.rst b/eng/vc-users.rst
index 31de516..64c2624 100644
--- a/eng/vc-users.rst
+++ b/eng/vc-users.rst
@@ -458,6 +458,14 @@ specify a version number for your patch, for example, use
to indicate the second version of a patch, ``-v3`` for a third, and so forth.
+Also, in order to create a patch specifying the repo name in the patch message,
+you should use the``--subject-prefix`` flag. For example, if contributing to
+the rtems-docs repo, use
+
+.. code-block:: shell
+
+ git format-patch --subject-prefix="PATCH rtems-docs" ...
+
Patches created using ``git format-patch`` are formatted so they can be emailed
and rely on having Git configured with your name and email address, for example