From: "Yu, Mingli" <mingli.yu@windriver.com>
To: Ross Burton <Ross.Burton@arm.com>,
"mingli.yu@eng.windriver.com" <mingli.yu@eng.windriver.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH 2/3] gnupg: Make the version consistent
Date: Mon, 22 Jan 2024 13:18:09 +0800 [thread overview]
Message-ID: <2841fb1e-17f3-79c8-762d-dfbd35723f24@windriver.com> (raw)
In-Reply-To: <72AFBC4A-9C2A-4181-8A8D-548855D2C870@arm.com>
Thanks Richard and Ross's comments!
I will try to send the patch to the upstream.
Thanks,
On 1/20/24 01:41, Ross Burton wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
>> On 19 Jan 2024, at 11:33, Yu, Mingli via lists.openembedded.org <mingli.yu=eng.windriver.com@lists.openembedded.org> wrote:
>> file://0004-autogen.sh-fix-find-version-for-beta-checking.patch \
>> file://0001-Woverride-init-is-not-needed-with-gcc-9.patch \
>> file://fix-ldap.patch \
>> + file://0001-autogen.sh-Remove-the-unknown-suffix.patch \
>
> 0004-autogen.sh-fix-find-version-for-beta-checking.patch already does something similar, so the patches should be merged instead of having a series of incremental fixes.
>
> Also, as RP said, engaging with upstream here would be good.
>
> Ross
next prev parent reply other threads:[~2024-01-22 5:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 11:33 [PATCH 1/3] xmlto: Remove the explicit PV setting mingli.yu
2024-01-19 11:33 ` [PATCH 2/3] gnupg: Make the version consistent mingli.yu
2024-01-19 11:43 ` [OE-core] " Richard Purdie
2024-01-19 17:41 ` Ross Burton
2024-01-22 5:18 ` Yu, Mingli [this message]
2024-01-19 11:33 ` [PATCH 3/3] libgcrypt: " mingli.yu
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=2841fb1e-17f3-79c8-762d-dfbd35723f24@windriver.com \
--to=mingli.yu@windriver.com \
--cc=Ross.Burton@arm.com \
--cc=mingli.yu@eng.windriver.com \
--cc=openembedded-core@lists.openembedded.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