From: Henning Schild <henning.schild@siemens.com>
To: Felix Moessbauer <felix.moessbauer@siemens.com>
Cc: <isar-users@googlegroups.com>, <adriaan.schmidt@siemens.com>
Subject: Re: [PATCH v3 0/2] Improve handling of ISAR_RELEASE_CMD
Date: Wed, 3 Nov 2021 19:20:36 +0100 [thread overview]
Message-ID: <20211103192036.46697642@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20211103123624.3015125-1-felix.moessbauer@siemens.com>
I would even go so far to include a patch that renames
do_rootfs_postprocess to do_rootfs_install_postprocess
Henning
Am Wed, 3 Nov 2021 13:36:22 +0100
schrieb Felix Moessbauer <felix.moessbauer@siemens.com>:
> Changes since v2:
>
> - fix bug in update_etc_os_release
> - Strip newlines from ISAR_RELEASE_CMD
>
> Changes since v1:
>
> - remove obsolete get_build_id function
>
> Felix Moessbauer (2):
> always invoke ISAR_RELEASE_CMD to invalidate downstream tasks on
> change
> Ensure generation of /etc/os-release is idempotent
>
> meta/classes/image-postproc-extension.bbclass | 6 ++--
> meta/classes/image.bbclass | 32
> ++++++++++--------- meta/classes/rootfs.bbclass |
> 2 +- 3 files changed, 21 insertions(+), 19 deletions(-)
>
prev parent reply other threads:[~2021-11-03 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-03 12:36 Felix Moessbauer
2021-11-03 12:36 ` [PATCH v3 1/2] always invoke ISAR_RELEASE_CMD to invalidate downstream tasks on change Felix Moessbauer
2021-11-03 13:42 ` Henning Schild
2021-11-03 14:09 ` Moessbauer, Felix
2021-11-03 18:16 ` Henning Schild
2021-11-04 11:50 ` Schmidt, Adriaan
2021-11-03 12:36 ` [PATCH v3 2/2] Ensure generation of /etc/os-release is idempotent Felix Moessbauer
2021-11-03 13:46 ` Henning Schild
2021-11-03 18:20 ` Henning Schild [this message]
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=20211103192036.46697642@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=adriaan.schmidt@siemens.com \
--cc=felix.moessbauer@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