From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Jörg Sommer" <joerg.sommer@navimatix.de>,
openembedded-core@lists.openembedded.org,
richard.purdie@linuxfoundation.org, ross.burton@arm.com,
rs@ti.com
Subject: Re: [PATCH v2] bitbake.conf: Extend distro feature usrmerge to merge bin+sbin
Date: Sat, 22 Aug 2026 14:16:41 +0200 [thread overview]
Message-ID: <DKVGRWKPI3K2.1PBICS35XGJYK@bootlin.com> (raw)
In-Reply-To: <aolV39x9UzHwcTrZ@navimatix.de>
On Sat Aug 22, 2026 at 9:56 AM CEST, Jörg Sommer wrote:
> Jörg Sommer schrieb am Fr 24. Jul, 11:00 (+0200):
>> From: Randolph Sapp <rs@ti.com>
>>
>> The split of bin and sbin became more artificial over time, and it is no
>> longer clear why programmes goes into the one or the other directory; e.g.
>> forever normal users have used sendmail in /usr/sbin, and fdisk and mkfs
>> learned to operate on files to create images long ago.
>
> Gentle ping. What's the state of this?
>
Hi Jörg,
Previous builds showed some errors. Should it have evolve since that?
Thanks,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2026-08-22 12:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-24 9:00 [PATCH v2] bitbake.conf: Extend distro feature usrmerge to merge bin+sbin Jörg Sommer
2026-07-25 7:34 ` [OE-core] " Mathieu Dubois-Briand
2026-08-22 7:56 ` Jörg Sommer
2026-08-22 12:16 ` Mathieu Dubois-Briand [this message]
2026-08-22 14:09 ` Jörg Sommer
2026-08-24 6:30 ` Mathieu Dubois-Briand
2026-08-24 9:53 ` Jörg Sommer
2026-08-24 10:02 ` Mathieu Dubois-Briand
2026-08-24 12:43 ` Jörg Sommer
2026-08-24 13:10 ` Mathieu Dubois-Briand
2026-08-24 12:48 ` [PATCH v3] " Jörg Sommer
2026-08-24 13:11 ` [OE-core] " Marko, Peter
2026-08-24 15:17 ` joerg.sommer
2026-08-24 16:18 ` Marko, Peter
2026-08-24 17:10 ` Richard Purdie
2026-08-25 7:33 ` Mathieu Dubois-Briand
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=DKVGRWKPI3K2.1PBICS35XGJYK@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=joerg.sommer@navimatix.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=ross.burton@arm.com \
--cc=rs@ti.com \
/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