patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Luca Boccassi <bluca@debian.org>
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] README: clarify the input of step 3
Date: Thu, 20 May 2021 21:59:48 +0200
Message-ID: <CAATJJ0J0Q9eYzXiEi3U3fY4-sUHVO7bfw_NyvPjR4n25vn7p2g@mail.gmail.com> (raw)
In-Reply-To: <d66d4fbf2e6f731d70c724cfbe4b1f385ad7cd8e.camel@debian.org>

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

      reply	other threads:[~2021-05-20 20:00 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
2021-05-20 19:59   ` 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=CAATJJ0J0Q9eYzXiEi3U3fY4-sUHVO7bfw_NyvPjR4n25vn7p2g@mail.gmail.com \
    --to=christian.ehrhardt@canonical.com \
    --cc=bluca@debian.org \
    --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

patches for DPDK stable branches

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/stable/0 stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ https://inbox.dpdk.org/stable \
		stable@dpdk.org
	public-inbox-index stable

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.stable


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git