[dpdk-stable] [scripts v2] README: fresh DPDK clone and main branch to generate list

[Xueming Li]

Appends notes of:
- git-log-fixes.sh needs to be free of conflicting tags.
- The script also expects current branch to contains end tag of range.


Signed-off-by: Xueming Li <xuemingl at nvidia.com>
---
 README | 16 +++++++++++-----
 1 file changed, 11 insertions(+), 5 deletions(-)

diff --git a/README b/README
index 70f4320..260e46e 100644
--- a/README
+++ b/README
@@ -26,11 +26,17 @@ as tmp dir for the patches and mails.
 1.A
 ---
 A list of commits to backport should be generated. This can be generated
-from "git-log-fixes.sh" script from DPDK. Normally the start of range is
-the end tag of last generated range, branch tag if working on the first
-stable release. The end of range is latest release tag. Assuming v17.11-rc1
-is out you can prepare a commit list for v17.08.1 stable release with:
-
+from "git-log-fixes.sh" script from DPDK. The repository this is executed
+in needs to be free of conflicting tags - since developers accumulate remote
+repositories, branches and tags a fresh git clone is the most reliable source
+to use. Normally the start of range is the end tag of last generated range,
+branch tag if working on the first stable release. The end of range is latest
+release tag. Assuming v17.11-rc1 is out, you should checkout a branch that
+contains end of range, normally main branch. Then prepare a commit list for
+v17.08.1 stable release with:
+
+    $ git clone http://dpdk.org/git/dpdk
+    $ cd dpdk
     $ ./devtools/git-log-fixes.sh v17.08..v17.11-rc1 > /tmp/list
 
 
-- 
2.25.1