From: Randolph Sapp <rs@ti.com>
To: Ross Burton <Ross.Burton@arm.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] Revert "gettext: fix a parallel build issue"
Date: Fri, 14 Mar 2025 13:32:17 -0500 [thread overview]
Message-ID: <D8G7CXG09QRC.WGDHGSSIY06R@ti.com> (raw)
In-Reply-To: <4AC93975-A859-47DE-844D-C4AD653BAA5D@arm.com>
On Fri Mar 14, 2025 at 1:13 PM CDT, Ross Burton wrote:
> On 14 Mar 2025, at 00:29, rs@ti.com wrote:
>>
>> From: Randolph Sapp <rs@ti.com>
>>
>> This reverts commit e18fc96f9d4c0a0525c21371d3f36e8dfe008b35.
>
> Can you explain why you’re reverting a fix for a build issue?
>
> Ross
Sorry about that. Please disregard this patch and "[OE-core] [PATCH] bzip2: add
libbz2.so.1.0 link for compat". I didn't notice my glob picked up some old
patches I was playing around with months ago. My bad.
- Randolph
next prev parent reply other threads:[~2025-03-14 18:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 0:29 [oe-core][RFC 0/3] Display manager proposal for x11 and wayland rs
2025-03-14 0:29 ` [PATCH] Revert "gettext: fix a parallel build issue" rs
2025-03-14 18:13 ` Ross Burton
2025-03-14 18:32 ` Randolph Sapp [this message]
2025-03-14 0:29 ` [PATCH] bzip2: add libbz2.so.1.0 link for compat rs
2025-03-14 0:29 ` [oe-core][RFC 1/3] emptty: add version 0.13.0 rs
2025-03-14 0:29 ` [oe-core][RFC 2/3] weston-init: convert to virtual-emptty-conf rs
2025-03-14 0:48 ` Patchtest results for " patchtest
2025-03-14 0:29 ` [oe-core][RFC 3/3] default-providers: set virtual-emptty-conf rs
[not found] ` <182C83EE5DCDDC9F.6194@lists.openembedded.org>
2025-03-14 0:39 ` [OE-core] [PATCH] Revert "gettext: fix a parallel build issue" Randolph Sapp
[not found] ` <182C83EDE0EF5771.27055@lists.openembedded.org>
2025-03-14 0:40 ` [OE-core] [PATCH] bzip2: add libbz2.so.1.0 link for compat Randolph Sapp
2025-03-14 9:14 ` [oe-core][RFC 0/3] Display manager proposal for x11 and wayland Alexander Kanavin
2025-03-14 19:14 ` Randolph Sapp
2025-03-15 0:36 ` Randolph Sapp
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=D8G7CXG09QRC.WGDHGSSIY06R@ti.com \
--to=rs@ti.com \
--cc=Ross.Burton@arm.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