patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Luca Boccassi <luca.boccassi@gmail.com>
Cc: dpdk stable <stable@dpdk.org>,
	Luca Boccassi <luca.boccassi@microsoft.com>
Subject: Re: [dpdk-stable] [scripts] 3-backport: use get-maintainer.sh to CC subtree maintainers
Date: Mon, 22 Feb 2021 17:26:27 +0100	[thread overview]
Message-ID: <CAATJJ0+6dvKwHdRyx=8_1XpU5i3-RrG9qLAuB13XVFR41S4E9g@mail.gmail.com> (raw)
In-Reply-To: <20210211135920.530256-1-luca.boccassi@gmail.com>

On Thu, Feb 11, 2021 at 2:59 PM <luca.boccassi@gmail.com> wrote:
>
> From: Luca Boccassi <luca.boccassi@microsoft.com>
>
> Signed-off-by: Luca Boccassi <luca.boccassi@microsoft.com>
> ---
>  3-request-backport | 8 +++++++-
>  README             | 4 ++++
>  2 files changed, 11 insertions(+), 1 deletion(-)

I haven't tested but from review this LGTM and we have together
expressed that we'd want this feature.
So Ack to it and if it exposes issues we can fix them up later.

Acked-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>

> diff --git a/3-request-backport b/3-request-backport
> index d123531..a1725e5 100755
> --- a/3-request-backport
> +++ b/3-request-backport
> @@ -2,6 +2,8 @@
>
>  source ./lib.sh
>
> +set -e
> +
>  list=""
>  if [ $# -lt 1 ] && [ "$GIT_AM_PAUSE_ON_FAIL" = "yes" ]
>  then
> @@ -13,7 +15,7 @@ then
>         for _file in $list
>         do
>                 _sub=$(grep Subject $_file | cut -d\  -f3-)
> -               echo "$_applied" | grep -qF "$_sub" || (head -n1 $_file | awk '{print $2}' >> /tmp/.list-$$)
> +               echo "$_applied" | grep -qF "$_sub" || (head -n1 $_file | awk -v _file=$_file '{print $2" "_file}' >> /tmp/.list-$$)
>         done
>         popd &>/dev/null
>  else
> @@ -33,6 +35,10 @@ get_cc_list()
>
>         > $cc_list
>         while read commit patch; do
> +               # Has to be used from git repository directory
> +               pushd $STABLE_DIR &>/dev/null
> +               $STABLE_DIR/devtools/get-maintainer.sh $patch >> $cc_list
> +               popd &>/dev/null
>                 $GIT show $commit | grep -h '^.*: .*<.*@.*\..*>' |
>                         sed 's/[^:]*: //' >> $cc_list
>         done < $list
> diff --git a/README b/README
> index 6489379..cc5f6bf 100644
> --- a/README
> +++ b/README
> @@ -120,6 +120,10 @@ should keep an accumulated list for the stable tree and send out this
>  request multiple times with the accumulated list of failed patches. This
>  list will also be used by "6-announce-release".
>
> +The 'devtools/get-maintainer.sh' tool from the DPDK repository is used to
> +compile the list of maintainers to CC for each patch. A configuration file
> +needs to be set up first, see the script itself for instructions.
> +
>  4-final-review
>  ==============
>
> --
> 2.29.2
>


-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd

      reply	other threads:[~2021-02-22 16:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-11 13:59 luca.boccassi
2021-02-22 16:26 ` Christian Ehrhardt [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='CAATJJ0+6dvKwHdRyx=8_1XpU5i3-RrG9qLAuB13XVFR41S4E9g@mail.gmail.com' \
    --to=christian.ehrhardt@canonical.com \
    --cc=luca.boccassi@gmail.com \
    --cc=luca.boccassi@microsoft.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).