From: Luca Boccassi <bluca@debian.org>
To: Christian Ehrhardt <christian.ehrhardt@canonical.com>,
stable@dpdk.org, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-stable] [PATCH] README: clarify that step 3 should run on latest main
Date: Thu, 20 May 2021 09:39:44 +0100 [thread overview]
Message-ID: <dab681d3cc6fb3999fb773e106dc3116e3ad9758.camel@debian.org> (raw)
In-Reply-To: <20210520081344.1973634-1-christian.ehrhardt@canonical.com>
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
next prev parent reply other threads:[~2021-05-20 8:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-20 8:13 Christian Ehrhardt
2021-05-20 8:39 ` Luca Boccassi [this message]
2021-05-20 20:00 ` 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=dab681d3cc6fb3999fb773e106dc3116e3ad9758.camel@debian.org \
--to=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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).