From: Patrick Ohly <patrick.ohly@intel.com>
To: "José Bollo" <jobol@nonadev.net>,
"wenzong fan" <wenzong.fan@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] shadow: 'useradd' copies root's extended attributes
Date: Thu, 04 Jan 2018 11:41:33 +0100 [thread overview]
Message-ID: <1515062493.10775.21.camel@intel.com> (raw)
In-Reply-To: <20180104111826.5c8f9036@d-jobol.iot.bzh>
On Thu, 2018-01-04 at 11:18 +0100, José Bollo wrote:
> > Do you agree to move the patch to Smack specific layer? Such as
> > meta-security?
>
> I agree.
Layers like meta-security should not modify recipes from other layers,
at least not by default. That would violate the "Yocto Compatible 2.0"
rules.
Besides, it would be harder to maintain in a separate layer - for the
maintainer of that layer.
I still think this patch belong into OE-core, even though it is then
more work for the OE-core maintainer.
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
next prev parent reply other threads:[~2018-01-04 10:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-09 14:07 [PATCH] shadow: 'useradd' copies root's extended attributes jobol
2017-03-09 16:07 ` Patrick Ohly
2017-03-09 16:48 ` José Bollo
2017-03-09 17:18 ` Patrick Ohly
2017-03-15 8:04 ` José Bollo
2018-01-04 9:28 ` wenzong fan
2018-01-04 9:31 ` wenzong fan
2018-01-04 10:18 ` José Bollo
2018-01-04 10:41 ` Patrick Ohly [this message]
2018-01-04 11:39 ` wenzong fan
2018-01-04 11:50 ` Patrick Ohly
2018-01-05 1:07 ` Fan, Wenzong
2018-01-09 17:01 ` Patrick Ohly
2018-01-10 9:50 ` wenzong fan
2018-01-15 14:33 ` José Bollo
2018-01-15 16:58 ` Patrick Ohly
2018-01-16 2:53 ` wenzong fan
2018-01-09 17:51 ` Mark Hatle
2018-01-10 11:15 ` Patrick Ohly
-- strict thread matches above, loose matches on Subject: below --
2017-03-13 9:57 jobol
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=1515062493.10775.21.camel@intel.com \
--to=patrick.ohly@intel.com \
--cc=jobol@nonadev.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=wenzong.fan@windriver.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