[dpdk-stable] [PATCH] README: clarify that step 3 should run on latest main

[dpdk-stable] [PATCH] README: clarify that step 3 should run on latest main

[Christian Ehrhardt]

Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
---
 README | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/README b/README
index 920cf3c..0f5ae88 100644
--- a/README
+++ b/README
@@ -126,6 +126,11 @@ 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.
 
+It is highly recommended to check out the most recent upstream/main branch
+in $STABLE_DIR as the tools will make use of the MAINTAINERS file found there.
+If not checking out the latest the generated addresses might be outdated and
+not reach the current maintainers.
+
 If you use GIT_AM_PAUSE_ON_FAIL="yes" you can call 3-request-backport without
 a list and it will process patches in xx.yy.z/tmp_import/list that it does
 not find as applied in the git history from the current head.
-- 
2.31.1

Re: [dpdk-stable] [PATCH] README: clarify that step 3 should run on latest main

[Luca Boccassi]

On Thu, 2021-05-20 at 10:13 +0200, Christian Ehrhardt wrote:
> Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> ---
>  README | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/README b/README
> index 920cf3c..0f5ae88 100644
> --- a/README
> +++ b/README
> @@ -126,6 +126,11 @@ 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.
>  
> +It is highly recommended to check out the most recent upstream/main branch
> +in $STABLE_DIR as the tools will make use of the MAINTAINERS file found there.
> +If not checking out the latest the generated addresses might be outdated and
> +not reach the current maintainers.
> +
>  If you use GIT_AM_PAUSE_ON_FAIL="yes" you can call 3-request-backport without
>  a list and it will process patches in xx.yy.z/tmp_import/list that it does
>  not find as applied in the git history from the current head.

Acked-by: Luca Boccassi <bluca@debian.org>

-- 
Kind regards,
Luca Boccassi

Re: [dpdk-stable] [PATCH] README: clarify that step 3 should run on latest main

[Christian Ehrhardt]

On Thu, May 20, 2021 at 10:39 AM Luca Boccassi <bluca@debian.org> wrote:
>
> On Thu, 2021-05-20 at 10:13 +0200, Christian Ehrhardt wrote:
> > Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> > ---
> >  README | 5 +++++
> >  1 file changed, 5 insertions(+)
> >
> > diff --git a/README b/README
> > index 920cf3c..0f5ae88 100644
> > --- a/README
> > +++ b/README
> > @@ -126,6 +126,11 @@ 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.
> >
> > +It is highly recommended to check out the most recent upstream/main branch
> > +in $STABLE_DIR as the tools will make use of the MAINTAINERS file found there.
> > +If not checking out the latest the generated addresses might be outdated and
> > +not reach the current maintainers.
> > +
> >  If you use GIT_AM_PAUSE_ON_FAIL="yes" you can call 3-request-backport without
> >  a list and it will process patches in xx.yy.z/tmp_import/list that it does
> >  not find as applied in the git history from the current head.
>
> Acked-by: Luca Boccassi <bluca@debian.org>

Thanks, pushed now together with the other outstanding changes to stable-scripts

> --
> Kind regards,
> Luca Boccassi



-- 
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd