public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: Henning Schild <work@hennsch.de>, isar-users@googlegroups.com
Cc: vijaikumar.kanagarajan@gmail.com,
	Henning Schild <henning.schild@siemens.com>
Subject: Re: [PATCH v2] meta: add quality check helper to image class
Date: Thu, 17 Mar 2022 16:52:14 +0300	[thread overview]
Message-ID: <6961c1c4-2e58-0582-1e6a-9a3429c50799@ilbers.de> (raw)
In-Reply-To: <20220303132553.31315-1-work@hennsch.de>

03.03.2022 16:25, Henning Schild wrote:
> From: Henning Schild <henning.schild@siemens.com>
>
> Content of rootfs should ideally all be coming from packages and their
> hooks. POSTPROCESSing and custom tasks should be handled with a lot of
> care and avoided where possible.
>
> This commit introduces a quality check task to help devs not
> accidentially abuse POSTPROCESS, while allowing them to add files to an
> ignore list.
>
> Signed-off-by: Henning Schild <henning.schild@siemens.com>

Applied to next, thanks.


      reply	other threads:[~2022-03-17 13:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-03 13:25 Henning Schild
2022-03-17 13:52 ` Anton Mikanovich [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=6961c1c4-2e58-0582-1e6a-9a3429c50799@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=vijaikumar.kanagarajan@gmail.com \
    --cc=work@hennsch.de \
    /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