[dpdk-stable] [PATCH] README: clarify the input of step 3

[dpdk-stable] [PATCH] README: clarify the input of step 3

[Christian Ehrhardt]

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

diff --git a/README b/README
index 70f4320..920cf3c 100644
--- a/README
+++ b/README
@@ -126,6 +126,14 @@ 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.
 
+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.
+
+If you want to manually keep lists the format needed is multiple lines of:
+  "commit-id path-to-patch-file"
+Patch files could be created via `git format-patch -1` or similar.
+
 4-final-review
 ==============
 
-- 
2.31.1

Re: [dpdk-stable] [PATCH] README: clarify the input of step 3

[Luca Boccassi]

On Tue, 2021-05-18 at 11:27 +0200, Christian Ehrhardt wrote:
> Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> ---
>  README | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/README b/README
> index 70f4320..920cf3c 100644
> --- a/README
> +++ b/README
> @@ -126,6 +126,14 @@ 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.
>  
> +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.
> +
> +If you want to manually keep lists the format needed is multiple lines of:
> +  "commit-id path-to-patch-file"
> +Patch files could be created via `git format-patch -1` or similar.
> +
>  4-final-review
>  ==============

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

-- 
Kind regards,
Luca Boccassi

Re: [dpdk-stable] [PATCH] README: clarify the input of step 3

[Christian Ehrhardt]

On Tue, May 18, 2021 at 2:56 PM Luca Boccassi <bluca@debian.org> wrote:
>
> On Tue, 2021-05-18 at 11:27 +0200, Christian Ehrhardt wrote:
> > Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> > ---
> >  README | 8 ++++++++
> >  1 file changed, 8 insertions(+)
> >
> > diff --git a/README b/README
> > index 70f4320..920cf3c 100644
> > --- a/README
> > +++ b/README
> > @@ -126,6 +126,14 @@ 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.
> >
> > +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.
> > +
> > +If you want to manually keep lists the format needed is multiple lines of:
> > +  "commit-id path-to-patch-file"
> > +Patch files could be created via `git format-patch -1` or similar.
> > +
> >  4-final-review
> >  ==============
>
> 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