From: Xueming Li <xuemingl@nvidia.com>
To: <stable@dpdk.org>, Luca Boccassi <bluca@debian.org>
Cc: Christian Ehrhardt <christian.ehrhardt@canonical.com>,
<xuemingl@nvidia.com>
Subject: [dpdk-stable] [scripts v2] README: fresh DPDK clone and main branch to generate list
Date: Mon, 10 May 2021 16:23:19 +0300 [thread overview]
Message-ID: <20210510132319.19207-1-xuemingl@nvidia.com> (raw)
In-Reply-To: <1619589811-9458-1-git-send-email-xuemingl@nvidia.com>
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@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
next prev parent reply other threads:[~2021-05-10 13:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1619589811-9458-1-git-send-email-xuemingl@nvidia.com>
2021-04-28 6:40 ` [dpdk-stable] [scripts] README: clean " Christian Ehrhardt
2021-05-06 13:21 ` Xueming(Steven) Li
[not found] ` <1620307153-12649-1-git-send-email-xuemingl@nvidia.com>
2021-05-06 16:05 ` [dpdk-stable] [scripts v2] README: fresh " Luca Boccassi
2021-05-10 13:23 ` Xueming Li [this message]
2021-05-10 13:27 ` Xueming(Steven) Li
2021-05-20 19:59 ` Christian Ehrhardt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210510132319.19207-1-xuemingl@nvidia.com \
--to=xuemingl@nvidia.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=stable@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).