patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] README: clarify the input of step 3
Date: Tue, 18 May 2021 13:56:02 +0100	[thread overview]
Message-ID: <d66d4fbf2e6f731d70c724cfbe4b1f385ad7cd8e.camel@debian.org> (raw)
In-Reply-To: <20210518092741.3544007-1-christian.ehrhardt@canonical.com>

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

  reply	other threads:[~2021-05-18 12:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18  9:27 Christian Ehrhardt
2021-05-18 12:56 ` Luca Boccassi [this message]
2021-05-20 19:59   ` Christian Ehrhardt

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=d66d4fbf2e6f731d70c724cfbe4b1f385ad7cd8e.camel@debian.org \
    --to=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.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).