From: Felix Moessbauer <felix.moessbauer@siemens.com>
To: <isar-users@googlegroups.com>
Cc: <henning.schild@siemens.com>,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [PATCH 0/1] Ensure generation of /etc/os-release is idempotent
Date: Wed, 9 Mar 2022 16:34:43 +0100 [thread overview]
Message-ID: <20220309153444.1885926-1-felix.moessbauer@siemens.com> (raw)
Please note that this fix originally was part of the
"Improve handling of ISAR_RELEASE_CMD" series.
This series is no longer relevant (due to recent changes in what is sstate-cached).
Hence, I re-send this as a standalone patch, because this fix is still required.
Best regards,
Felix
Felix Moessbauer (1):
Ensure generation of /etc/os-release is idempotent
meta/classes/image-postproc-extension.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--
2.30.2
next reply other threads:[~2022-03-09 15:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 15:34 Felix Moessbauer [this message]
2022-03-09 15:34 ` [PATCH 1/1] " Felix Moessbauer
2022-03-10 8:07 ` Henning Schild
2022-03-21 15:00 ` [PATCH 0/1] " Anton Mikanovich
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=20220309153444.1885926-1-felix.moessbauer@siemens.com \
--to=felix.moessbauer@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