From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Josh Soref <jsoref@gmail.com>
Cc: dpdk stable <stable@dpdk.org>
Subject: Re: please help backporting some patches to stable release 19.11.12 - part II
Date: Wed, 9 Mar 2022 08:49:20 +0100 [thread overview]
Message-ID: <CAATJJ0LiMHrqUE+m2L3BNoPwwpcUYVAyr8A_sua+U-1Wrrd6WA@mail.gmail.com> (raw)
In-Reply-To: <CACZqfqC96L3QDgztNXPwwrGv+ah_JpGTW+gEnx+SEO-9Od8Qjw@mail.gmail.com>
On Fri, Feb 25, 2022 at 6:54 PM Josh Soref <jsoref@gmail.com> wrote:
>
> Christian Ehrhardt wrote:
>
> 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 19.11
> stable branch, as conflicts or build errors occur.
>
> Can authors check your patches in the following list and either:
> - Backport your patches to the 19.11 branch, or
> - Indicate that the patch should not be backported
>
>
> My spelling work can be safely skipped.
Thank you for the FYI
Maybe to everyone let me explain the reason why we even try :-)
In general those kinds of fixes are not "too important" but if they
can be applied it keeps the amount of extra churn lower later on.
Imagine you touch every string with a commit, afterwards nothing will
apply automatically anymore.
So sometimes backporting those changes even if they feel "not
important" can help.
>> Please do either of the above by 03/11/22.
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
next prev parent reply other threads:[~2022-03-09 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220225171532.3498996-1-christian.ehrhardt@canonical.com>
2022-02-25 17:53 ` Josh Soref
2022-03-09 7:49 ` Christian Ehrhardt [this message]
2022-03-09 12:47 ` Josh Soref
2022-03-07 15:15 ` Kalesh Anakkur Purayil
2022-03-09 7:53 ` 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=CAATJJ0LiMHrqUE+m2L3BNoPwwpcUYVAyr8A_sua+U-1Wrrd6WA@mail.gmail.com \
--to=christian.ehrhardt@canonical.com \
--cc=jsoref@gmail.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).