From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH 0/3] fix and test wic exclude-path
Date: Fri, 12 Jun 2020 20:46:44 +0200 [thread overview]
Message-ID: <19ffe293-3a99-27c0-3aa0-686be92a1df7@siemens.com> (raw)
In-Reply-To: <20200612202202.3c17bc8c@md1za8fc.ad001.siemens.net>
On 12.06.20 20:22, Henning Schild wrote:
> Am Fri, 12 Jun 2020 17:17:19 +0200
> schrieb "[ext] Jan Kiszka" <jan.kiszka@siemens.com>:
>
>> On 12.06.20 08:55, Baurzhan Ismagulov wrote:
>>> Hello Henning,
>>>
>>> On Wed, Jun 10, 2020 at 05:26:27PM +0200, Henning Schild wrote:
>>>> Still having to work around that in a downstream layer. Any more
>>>> comments or questions?
>>>
>>> I'd like to look at the following issues:
>>>
>>> 1. I'd like to understand what exactly is failing when the fix is
>>> not applied.
>>>
>>> 2. The test case is failing with the fix applied.
>>>
>>
>> Before we dig too deep on details:
>>
>> The pressure to update wic to a more recent version is increasing,
>> just received another request today,
>
> Which feature did the request care about? If it is the exclude, we
> might me able to stall the inevitable ...
--use-uuid for non-rootfs partitions.
In addition, not only /me would like to get rid of
https://github.com/siemens/meta-iot2050/blob/jan/upstream-u-boot/isar-patches/0001-wic-Ensure-that-sourceparams-values-can-contain.patch
in downstream.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2020-06-12 18:46 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 20:16 Henning Schild
2020-04-06 20:16 ` [PATCH 1/3] oe.path: Add copyhardlink() helper function Henning Schild
2020-04-06 20:16 ` [PATCH 2/3] lib/oe/path: try hardlinking instead of guessing when it might fail Henning Schild
2020-04-06 20:16 ` [PATCH 3/3] CI: test the exclude-path feature of wic Henning Schild
2020-05-07 19:25 ` Baurzhan Ismagulov
2020-05-07 20:13 ` Henning Schild
2020-09-01 19:54 ` [PATCH v2 " Baurzhan Ismagulov
2020-09-02 5:30 ` vijaikumar....@gmail.com
2020-09-02 10:10 ` Henning Schild
2020-04-06 20:18 ` [PATCH 0/3] fix and test wic exclude-path Henning Schild
2020-06-10 15:26 ` Henning Schild
2020-06-12 6:55 ` Baurzhan Ismagulov
2020-06-12 15:17 ` Jan Kiszka
2020-06-12 18:11 ` Henning Schild
2020-06-12 18:17 ` Henning Schild
2020-06-12 18:44 ` Jan Kiszka
2020-06-12 18:22 ` Henning Schild
2020-06-12 18:46 ` Jan Kiszka [this message]
2020-06-12 18:03 ` Henning Schild
2020-09-01 19:53 ` Baurzhan Ismagulov
2020-09-02 5:24 ` vijaikumar....@gmail.com
2020-09-02 10:04 ` Henning Schild
2020-09-14 13:36 ` Baurzhan Ismagulov
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=19ffe293-3a99-27c0-3aa0-686be92a1df7@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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