From: Seebs <seebs@seebs.net>
To: Patrick Ohly <patrick.ohly@intel.com>
Cc: OpenEmbedded <openembedded-core@lists.openembedded.org>
Subject: Re: host-user-contaminated QA check
Date: Thu, 2 Feb 2017 14:06:14 -0600 [thread overview]
Message-ID: <20170202140614.37db286c@seebsdell> (raw)
In-Reply-To: <1486064629.14889.62.camel@intel.com>
On Thu, 02 Feb 2017 20:43:49 +0100
Patrick Ohly <patrick.ohly@intel.com> wrote:
> One could argue that an implicit "created during build -> owned by
> root" follows the same logic. But as the check as it is now did find
> a real issue and also others in the past (the pseudo bugs that Chris
> mentioned), let's keep it.
I am somewhat inclined to change pseudo's default to "if there's no
entry, report something definitely invalid", or make that an available
option, because that would avoid false positives, and allow a more
rigorous QA check.
-s
next prev parent reply other threads:[~2017-02-02 20:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 10:38 host-user-contaminated QA check Patrick Ohly
2017-02-02 16:21 ` Seebs
2017-02-02 16:39 ` Patrick Ohly
2017-02-02 17:12 ` Seebs
2017-02-02 17:17 ` Patrick Ohly
2017-02-02 17:52 ` Christopher Larson
2017-02-02 19:11 ` Seebs
2017-02-02 19:43 ` Patrick Ohly
2017-02-02 20:06 ` Seebs [this message]
2017-02-02 17:49 ` Enrico Scholz
2017-02-02 19:29 ` Patrick Ohly
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=20170202140614.37db286c@seebsdell \
--to=seebs@seebs.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=patrick.ohly@intel.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 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.