[dpdk-stable] [PATCH 2/2] 3-request-backport: explain why patches are selected

[christian.ehrhardt@canonical.com]

From: Christian Ehrhardt <christian.ehrhardt@canonical.com>

In the past we had a few "hey why did you try in the first place".
Since this is done based on the DPDK managed tool ./devtools/git-log-fixes.sh
discussions improvements and changes need to happen there and not on the
mail that that asks for backports.
Therefore mention the tool that selected the initial patch list in the
DPDK LTS process to guide everyone there as needed.

Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
---
 3-request-backport | 1 +
 1 file changed, 1 insertion(+)

diff --git a/3-request-backport b/3-request-backport
index 67234d2..eafd31e 100755
--- a/3-request-backport
+++ b/3-request-backport
@@ -58,6 +58,7 @@ cat << EOF
 
 Hi commit authors (and maintainers),
 
+Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh
 I didn't apply following commits from DPDK main to $stable_branch
 $(stable_or_lts) branch, as conflicts or build errors occur.
 
-- 
2.32.0