From: Xueming Li <xuemingl@nvidia.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Cc: Christian Ehrhardt <christian.ehrhardt@canonical.com>,
"bluca@debian.org" <bluca@debian.org>,
"ktraynor@redhat.com" <ktraynor@redhat.com>,
"stable@dpdk.org" <stable@dpdk.org>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v3 2/2] devtools: fix patches missing if range newer than HEAD
Date: Wed, 21 Aug 2024 13:51:56 +0000 [thread overview]
Message-ID: <CH3PR12MB8658CA45CABE196BD906B0B9A18E2@CH3PR12MB8658.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20240815093245.7453bcbf@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
Not really needed, check out the main branch can avoid such issue. Thanks for looking into this.
________________________________
From: Stephen Hemminger <stephen@networkplumber.org>
Sent: Friday, August 16, 2024 12:32 AM
To: NBU-Contact-Thomas Monjalon (EXTERNAL) <thomas@monjalon.net>
Cc: Christian Ehrhardt <christian.ehrhardt@canonical.com>; bluca@debian.org <bluca@debian.org>; ktraynor@redhat.com <ktraynor@redhat.com>; stable@dpdk.org <stable@dpdk.org>; dev@dpdk.org <dev@dpdk.org>; Xueming Li <xuemingl@nvidia.com>
Subject: Re: [dpdk-stable] [PATCH v3 2/2] devtools: fix patches missing if range newer than HEAD
On Sat, 26 Nov 2022 22:44:26 +0100
Thomas Monjalon <thomas@monjalon.net> wrote:
> Someone to help with review of this patch please?
> Is there a real need?
>
>
The patch looks ok, but no longer applies, needs to be rebased.
Xueming if you are still needing this resubmit please.
>
[-- Attachment #2: Type: text/html, Size: 1819 bytes --]
prev parent reply other threads:[~2024-08-21 13:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-12 13:56 [dpdk-stable] [PATCH 1/2] devtools: fix version pattern for fix search Xueming Li
2021-06-12 13:56 ` [dpdk-stable] [PATCH 2/2] devtools: auto detect branch to search fix patches Xueming Li
2021-06-14 14:15 ` Christian Ehrhardt
2021-06-15 10:56 ` Xueming(Steven) Li
2021-06-30 6:46 ` Xueming(Steven) Li
2021-06-14 13:56 ` [dpdk-stable] [PATCH 1/2] devtools: fix version pattern for fix search Christian Ehrhardt
2021-06-16 4:03 ` [dpdk-stable] [PATCH v1 " Xueming Li
2021-06-30 6:34 ` [dpdk-stable] [PATCH v2 " Xueming Li
2021-06-30 6:34 ` [dpdk-stable] [PATCH v2 2/2] devtools: fix patches missing if range newer than HEAD Xueming Li
2021-08-08 11:24 ` Thomas Monjalon
2021-08-09 7:44 ` Xueming(Steven) Li
2021-08-08 11:14 ` [dpdk-stable] [PATCH v2 1/2] devtools: fix version pattern for fix search Thomas Monjalon
2021-08-09 3:32 ` Xueming(Steven) Li
2021-06-16 4:03 ` [dpdk-stable] [PATCH v1 2/2] devtools: auto detect branch to search fix patches Xueming Li
2021-08-11 11:22 ` [dpdk-stable] [PATCH v3 1/2] devtools: fix version pattern for fix search Xueming Li
2021-08-11 11:22 ` [dpdk-stable] [PATCH v3 2/2] devtools: fix patches missing if range newer than HEAD Xueming Li
2022-11-26 21:44 ` Thomas Monjalon
2024-08-15 16:32 ` Stephen Hemminger
2024-08-21 13:51 ` Xueming Li [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=CH3PR12MB8658CA45CABE196BD906B0B9A18E2@CH3PR12MB8658.namprd12.prod.outlook.com \
--to=xuemingl@nvidia.com \
--cc=bluca@debian.org \
--cc=christian.ehrhardt@canonical.com \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.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).