patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Xueming Li <xuemingl@nvidia.com>, stable@dpdk.org
Cc: Christian Ehrhardt <christian.ehrhardt@canonical.com>
Subject: Re: [dpdk-stable] [scripts] README: add hint on commit range to generate backport list
Date: Tue, 02 Mar 2021 10:25:46 +0000	[thread overview]
Message-ID: <2046e42c8d529a8dfca1c3f395c3a6733093082e.camel@debian.org> (raw)
In-Reply-To: <20210302064725.22965-1-xuemingl@nvidia.com>

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

      reply	other threads:[~2021-03-02 10:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02  6:47 Xueming Li
2021-03-02 10:25 ` Luca Boccassi [this message]

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=2046e42c8d529a8dfca1c3f395c3a6733093082e.camel@debian.org \
    --to=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=stable@dpdk.org \
    --cc=xuemingl@nvidia.com \
    /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).