alioth/nixpkgs
3
0
Fork 0
forked from mirrors/nixpkgs
Code Releases Activity

doc/contributing: mention the word “backporting” for grep-ability

Browse source 
When a contributor wants to know how to do this ominous “backporting”
everybody is talking about, a grep should be enough to find it.
This commit is contained in:
Profpatsch 2019-11-15 15:05:42 +01:00
parent 50d06185ca
commit 85c2bb3781
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
doc/contributing/submitting-changes.xml
View file

@ -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: