From: Luca Boccassi <luca.boccassi@gmail.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, stable@dpdk.org, Yuanhan Liu <yliu@fridaylinux.org>
Subject: Re: [PATCH 1/2] devtools: fix check of multiple commits fixed at once
Date: Tue, 28 Nov 2023 14:15:16 +0000 [thread overview]
Message-ID: <CAMw=ZnQYXHygBS6kL7++BtH2yVbQyuDQLk5Gfx6jFcT=31yZUg@mail.gmail.com> (raw)
In-Reply-To: <20230418140726.1472209-2-thomas@monjalon.net>
On Tue, 18 Apr 2023 at 15:08, Thomas Monjalon <thomas@monjalon.net> wrote:
>
> When looking for fixes to backport,
> only the first origin commit hash (from "Fixes:") was checked.
> There is very little chance that the next commits being fixed
> have a wrong hash in the commit log of the fix,
> but it is fixed by checking them all before proceeding further.
>
> Fixes: 752d8e097ec1 ("scripts: show fixes with release version of bug")
> Cc: stable@dpdk.org
>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> devtools/git-log-fixes.sh | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Acked-by: Luca Boccassi <bluca@debian.org>
prev parent reply other threads:[~2023-11-28 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230418140726.1472209-1-thomas@monjalon.net>
2023-04-18 14:07 ` Thomas Monjalon
2023-11-28 14:15 ` Luca Boccassi [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='CAMw=ZnQYXHygBS6kL7++BtH2yVbQyuDQLk5Gfx6jFcT=31yZUg@mail.gmail.com' \
--to=luca.boccassi@gmail.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
--cc=yliu@fridaylinux.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).