* [dpdk-stable] [scripts] README: add hint on commit range to generate backport list
@ 2021-03-02 6:47 Xueming Li
2021-03-02 10:25 ` Luca Boccassi
0 siblings, 1 reply; 2+ messages in thread
From: Xueming Li @ 2021-03-02 6:47 UTC (permalink / raw)
To: stable, Luca Boccassi; +Cc: Christian Ehrhardt
Adds tip of the commit range to generate backport list.
Signed-off-by: Xueming Li <xuemingl@nvidia.com>
---
README | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/README b/README
index 6489379..e9795b5 100644
--- a/README
+++ b/README
@@ -26,8 +26,10 @@ 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. 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. 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:
$ ./devtools/git-log-fixes.sh v17.08..v17.11-rc1 > /tmp/list
--
2.25.1
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [dpdk-stable] [scripts] README: add hint on commit range to generate backport list
2021-03-02 6:47 [dpdk-stable] [scripts] README: add hint on commit range to generate backport list Xueming Li
@ 2021-03-02 10:25 ` Luca Boccassi
0 siblings, 0 replies; 2+ messages in thread
From: Luca Boccassi @ 2021-03-02 10:25 UTC (permalink / raw)
To: Xueming Li, stable; +Cc: Christian Ehrhardt
On Tue, 2021-03-02 at 14:47 +0800, Xueming Li wrote:
> Adds tip of the commit range to generate backport list.
>
> Signed-off-by: Xueming Li <xuemingl@nvidia.com>
> ---
> README | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/README b/README
> index 6489379..e9795b5 100644
> --- a/README
> +++ b/README
> @@ -26,8 +26,10 @@ 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. 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. 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:
>
> $ ./devtools/git-log-fixes.sh v17.08..v17.11-rc1 > /tmp/list
Acked-by: Luca Boccassi <bluca@debian.org>
Thank you, applied and pushed
--
Kind regards,
Luca Boccassi
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-03-02 10:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-02 6:47 [dpdk-stable] [scripts] README: add hint on commit range to generate backport list Xueming Li
2021-03-02 10:25 ` Luca Boccassi
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).