From: "Aleksandar Nikolic" <an010@live.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>,yocto@lists.yoctoproject.org
Subject: Re: [yocto] Multiple images on the same hardware
Date: Thu, 25 Jan 2024 07:05:09 -0800 [thread overview]
Message-ID: <27265.1706195109545788026@lists.yoctoproject.org> (raw)
In-Reply-To: <CANNYZj8EwssU2_QbnxUg_GAvbjWwrhD7bkV2H9uoi2ogSrT7-Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 141 bytes --]
As I thought, thanks. I guess I'll try bbappend-ing the recipe in the respective product layers and see where that brings me.
Aleksandar
[-- Attachment #2: Type: text/html, Size: 149 bytes --]
next prev parent reply other threads:[~2024-01-25 15:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 9:38 Multiple images on the same hardware Aleksandar Nikolic
2024-01-25 9:55 ` [yocto] " Alexander Kanavin
2024-01-25 12:18 ` Aleksandar Nikolic
2024-01-25 14:54 ` Alexander Kanavin
2024-01-25 15:05 ` Aleksandar Nikolic [this message]
2024-01-31 7:23 ` Mike Looijmans
2024-01-31 22:07 ` Aleksandar Nikolic
2024-02-01 13:55 ` Mike Looijmans
2024-02-01 14:11 ` Aleksandar Nikolic
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=27265.1706195109545788026@lists.yoctoproject.org \
--to=an010@live.com \
--cc=alex.kanavin@gmail.com \
--cc=yocto@lists.yoctoproject.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