From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>,
Martyn Welch <martyn.welch@collabora.co.uk>
Cc: yocto@yoctoproject.org, openembedded-core@lists.openembedded.org
Subject: Re: [yocto] [PATCH v4 1/3] image.bbclass: add prohibited-paths QA test
Date: Fri, 17 Nov 2017 09:15:37 +0200 [thread overview]
Message-ID: <cb78b834-b34d-2b85-d4c3-e2081f90a83e@linux.intel.com> (raw)
In-Reply-To: <20171116172129.11b89562@lsandov1-mobl2.zpn.intel.com>
On 11/17/2017 01:21 AM, Leonardo Sandoval wrote:
> isn't it this class meta/classes/insane.bbclass for this type of checks?
This was already discussed - the test should be on the image rather than
package level:
http://lists.openembedded.org/pipermail/openembedded-core/2017-November/144335.html
Alex
WARNING: multiple messages have this Message-ID (diff)
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>,
Martyn Welch <martyn.welch@collabora.co.uk>
Cc: yocto@yoctoproject.org, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH v4 1/3] image.bbclass: add prohibited-paths QA test
Date: Fri, 17 Nov 2017 09:15:37 +0200 [thread overview]
Message-ID: <cb78b834-b34d-2b85-d4c3-e2081f90a83e@linux.intel.com> (raw)
In-Reply-To: <20171116172129.11b89562@lsandov1-mobl2.zpn.intel.com>
On 11/17/2017 01:21 AM, Leonardo Sandoval wrote:
> isn't it this class meta/classes/insane.bbclass for this type of checks?
This was already discussed - the test should be on the image rather than
package level:
http://lists.openembedded.org/pipermail/openembedded-core/2017-November/144335.html
Alex
next prev parent reply other threads:[~2017-11-17 7:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 15:05 [PATCH v4 1/3] image.bbclass: add prohibited-paths QA test Martyn Welch
2017-11-16 15:05 ` [PATCH v4 2/3] core-image.bbclass: add default IMAGE_QA_PROHIBIT_PATHS variable Martyn Welch
2017-11-16 15:05 ` [PATCH v4 3/3] ref-manual: Add documentation for prohibited-path QA test Martyn Welch
2017-11-16 17:58 ` [PATCH v4 1/3] image.bbclass: add prohibited-paths " Otavio Salvador
2017-11-16 17:58 ` [OE-core] " Otavio Salvador
2017-11-17 10:02 ` Martyn Welch
2017-11-17 10:02 ` [OE-core] " Martyn Welch
2017-11-16 23:21 ` [yocto] " Leonardo Sandoval
2017-11-16 23:21 ` Leonardo Sandoval
2017-11-17 7:15 ` Alexander Kanavin [this message]
2017-11-17 7:15 ` [OE-core] " Alexander Kanavin
2017-11-17 10:06 ` [yocto] " Martyn Welch
2017-11-17 10:06 ` Martyn Welch
2017-11-17 11:56 ` [yocto] " Otavio Salvador
2017-11-17 11:56 ` [OE-core] " Otavio Salvador
2017-11-17 22:53 ` ✗ patchtest: failure for "[v4] image.bbclass: add prohib..." and 2 more Patchwork
2017-11-18 0:11 ` Patchwork
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=cb78b834-b34d-2b85-d4c3-e2081f90a83e@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=leonardo.sandoval.gonzalez@linux.intel.com \
--cc=martyn.welch@collabora.co.uk \
--cc=openembedded-core@lists.openembedded.org \
--cc=yocto@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.