summary refs log tree commit diff
path: root/doc
diff options
context:
space:
mode:
authorProfpatsch <mail@profpatsch.de>2019-11-15 15:05:42 +0100
committerProfpatsch <mail@profpatsch.de>2019-11-15 15:06:54 +0100
commit85c2bb37816dd79724a27ce7b97647a2ebf21ec0 (patch)
tree601390955505b2a9ec730681430c70c148e3b86d /doc
parent50d06185cafa6232dd3a317bbf87f2f7d1b2b453 (diff)
downloadnixpkgs-85c2bb37816dd79724a27ce7b97647a2ebf21ec0.tar
nixpkgs-85c2bb37816dd79724a27ce7b97647a2ebf21ec0.tar.gz
nixpkgs-85c2bb37816dd79724a27ce7b97647a2ebf21ec0.tar.bz2
nixpkgs-85c2bb37816dd79724a27ce7b97647a2ebf21ec0.tar.lz
nixpkgs-85c2bb37816dd79724a27ce7b97647a2ebf21ec0.tar.xz
nixpkgs-85c2bb37816dd79724a27ce7b97647a2ebf21ec0.tar.zst
nixpkgs-85c2bb37816dd79724a27ce7b97647a2ebf21ec0.zip
doc/contributing: mention the word “backporting” for grep-ability
When a contributor wants to know how to do this ominous “backporting”
everybody is talking about, a grep should be enough to find it.
Diffstat (limited to 'doc')
-rw-r--r--doc/contributing/submitting-changes.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/contributing/submitting-changes.xml b/doc/contributing/submitting-changes.xml
index 6a8b4e0b249..950e1ea974a 100644
--- a/doc/contributing/submitting-changes.xml
+++ b/doc/contributing/submitting-changes.xml
@@ -441,7 +441,7 @@ Additional information.
    <itemizedlist>
     <listitem>
      <para>
-      If you're cherry-picking a commit to a stable release branch, always use <command>git cherry-pick -xe</command> and ensure the message contains a clear description about why this needs to be included in the stable branch.
+      If you're cherry-picking a commit to a stable release branch (“backporting”), always use <command>git cherry-pick -xe</command> and ensure the message contains a clear description about why this needs to be included in the stable branch.
      </para>
      <para>
       An example of a cherry-picked commit would look like this: