From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Luca Boccassi <bluca@debian.org>
Cc: dpdk stable <stable@dpdk.org>,
Thomas Monjalon <thomas@monjalon.net>,
Xueming Li <xuemingl@nvidia.com>
Subject: Re: [dpdk-stable] [PATCH 2/2] 3-request-backport: explain why patches are selected
Date: Wed, 11 Aug 2021 08:38:30 +0200 [thread overview]
Message-ID: <CAATJJ0J7TeQx5jFJFYKa2V56mdQZvTsMzFBf0HhNV5xZcXJ4hQ@mail.gmail.com> (raw)
In-Reply-To: <7416f78986ac6f39627befaab156114e96478ebb.camel@debian.org>
On Tue, Aug 10, 2021 at 6:58 PM Luca Boccassi <bluca@debian.org> wrote:
>
> On Tue, 2021-08-10 at 16:24 +0200, christian.ehrhardt@canonical.com
> wrote:
> > From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> >
> > In the past we had a few "hey why did you try in the first place".
> > Since this is done based on the DPDK managed tool ./devtools/git-log-fixes.sh
> > discussions improvements and changes need to happen there and not on the
> > mail that that asks for backports.
> > Therefore mention the tool that selected the initial patch list in the
> > DPDK LTS process to guide everyone there as needed.
> >
> > Signed-off-by: Christian Ehrhardt <christian.ehrhardt@canonical.com>
> > ---
> > 3-request-backport | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/3-request-backport b/3-request-backport
> > index 67234d2..eafd31e 100755
> > --- a/3-request-backport
> > +++ b/3-request-backport
> > @@ -58,6 +58,7 @@ cat << EOF
> >
> > Hi commit authors (and maintainers),
> >
> > +Despite being selected by the DPDK maintenance tool ./devtools/git-log-fixes.sh
> > I didn't apply following commits from DPDK main to $stable_branch
> > $(stable_or_lts) branch, as conflicts or build errors occur.
>
> Acked-by: Luca Boccassi <bluca@debian.org>
Thanks, applied now
> --
> Kind regards,
> Luca Boccassi
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
next prev parent reply other threads:[~2021-08-11 6:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 14:24 [dpdk-stable] [PATCH 1/2] 3-request-backport: use history from stable branch christian.ehrhardt
2021-08-10 14:24 ` [dpdk-stable] [PATCH 2/2] 3-request-backport: explain why patches are selected christian.ehrhardt
2021-08-10 16:58 ` Luca Boccassi
2021-08-11 6:38 ` Christian Ehrhardt [this message]
2021-08-10 16:57 ` [dpdk-stable] [PATCH 1/2] 3-request-backport: use history from stable branch Luca Boccassi
2021-08-11 6:38 ` 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=CAATJJ0J7TeQx5jFJFYKa2V56mdQZvTsMzFBf0HhNV5xZcXJ4hQ@mail.gmail.com \
--to=christian.ehrhardt@canonical.com \
--cc=bluca@debian.org \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=xuemingl@nvidia.com \
/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).