From: "Martin Siegumfeldt" <mns@gomspace.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 2/2] systemd: add shell-profile-dropins PACKAGECONFIG
Date: Sun, 05 Apr 2026 07:04:18 -0700 [thread overview]
Message-ID: <275547.1775397858027409536@lists.openembedded.org> (raw)
In-Reply-To: <cd8d7975-9631-4cce-b3d4-b9644e968606@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 212 bytes --]
I just tested current master which is on systemd 259.5. It includes the mentioned commits, however OSC injections still occur. Was there any particular config in mind that would disable them?
Thanks,
Martin
[-- Attachment #2: Type: text/html, Size: 262 bytes --]
next prev parent reply other threads:[~2026-04-05 14:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 2:19 [OE-core][PATCH 1/2] systemd: do not let do_fetch depend on PACKAGECONFIG Qi.Chen
2026-01-15 2:19 ` [OE-core][PATCH 2/2] systemd: add shell-profile-dropins PACKAGECONFIG Qi.Chen
2026-01-23 13:06 ` Paul Barker
2026-01-28 2:47 ` ChenQi
2026-04-05 14:04 ` Martin Siegumfeldt [this message]
2026-01-26 12:54 ` Ross Burton
2026-01-27 9:09 ` Chen, Qi
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=275547.1775397858027409536@lists.openembedded.org \
--to=mns@gomspace.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