One, HEAD~, not HEAD, should be used to generate any patches. Two, add "ovn" to the generated mail topic. Third, update branch name to a fresh one.
Signed-off-by: Ihar Hrachyshka <ihrac...@redhat.com> --- Documentation/internals/contributing/backporting-patches.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/internals/contributing/backporting-patches.rst b/Documentation/internals/contributing/backporting-patches.rst index b10c9d7b0..b5232bb51 100644 --- a/Documentation/internals/contributing/backporting-patches.rst +++ b/Documentation/internals/contributing/backporting-patches.rst @@ -68,7 +68,7 @@ patch, for example: :: - $ git format-patch HEAD --subject-prefix="PATCH branch-2.7" + $ git format-patch HEAD~ --subject-prefix="PATCH ovn branch-21.06" If a maintainer is backporting a change to older branches and the backport is not a trivial cherry-pick, then the maintainer may opt to submit the backport -- 2.31.1 _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
