From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>,
Quirin Gylstorff <quirin.gylstorff@siemens.com>
Subject: Re: [PATCH] images: Complete account related exceptions in do_rootfs_quality_check
Date: Fri, 10 Feb 2023 20:45:01 +0100 [thread overview]
Message-ID: <20230210204501.1efeebe5@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <4fe96d1a-0e9f-ac8b-7f65-582ef6b33bd3@siemens.com>
Kind of hard to read what was changed and the commit message is also
not too verbose. I think i get it so ACK.
But i would suggest to sort that list in a p1 alphabetically ... no
change just sort.
And later do the real change in a p2.
You sort and add in one patch, which makes it hard to review.
Henning
Am Fri, 10 Feb 2023 20:19:03 +0100
schrieb Jan Kiszka <jan.kiszka@siemens.com>:
> From: Jan Kiszka <jan.kiszka@siemens.com>
>
> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> ---
> meta/classes/image.bbclass | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 539ec51d..ef7d5a2a 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -482,10 +482,12 @@ do_rootfs_quality_check() {
> args="${args} ! -path ${ROOTFSDIR}/etc/passwd \
> ! -path ${ROOTFSDIR}/etc/subgid \
> ! -path ${ROOTFSDIR}/etc/subuid \
> - ! -path ${ROOTFSDIR}/etc/shadow- \
> ! -path ${ROOTFSDIR}/etc/gshadow \
> + ! -path ${ROOTFSDIR}/etc/gshadow- \
> ! -path ${ROOTFSDIR}/etc/shadow \
> - ! -path ${ROOTFSDIR}/etc/group"
> + ! -path ${ROOTFSDIR}/etc/shadow- \
> + ! -path ${ROOTFSDIR}/etc/group \
> + ! -path ${ROOTFSDIR}/etc/group-"
> ;;
> esac
> done
next prev parent reply other threads:[~2023-02-10 19:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 19:19 Jan Kiszka
2023-02-10 19:45 ` Henning Schild [this message]
2023-02-16 4:38 ` Uladzimir Bely
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=20230210204501.1efeebe5@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=quirin.gylstorff@siemens.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