Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Yi Zhao <yi.zhao@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][PATCH 0/4] host-user-contaminated fixes for meta-oe
Date: Fri, 15 Jan 2016 15:19:15 +0800	[thread overview]
Message-ID: <56989D73.8080303@windriver.com> (raw)
In-Reply-To: <569776A1.4000205@topic.nl>



在 2016年01月14日 18:21, Mike Looijmans 写道:
> Instead of patching things up with chown, you could also instruct the 
> "cp" command to not attempt to preserve ownership (the -a and -p 
> options will do that).
>
> Instead of "cp -r -p ..." use "cp -r --preserve=mode,links ..."
>
> Instead of "cp -a ..." use "cp -R --no-dereference 
> --preserve=mode,links ..."
>
> This fixes these QA warnings in a more structured way.
>

Thanks, Mike

I will send V2 patch.

Yi


>
> On 14-01-16 09:19, Yi Zhao wrote:
>>
>> The following changes since commit 
>> 73af5c278f6617149a46b2d2a1549bc154fa79e5:
>>
>>    mime-construct: Perform more mangling for perl path (2016-01-06 
>> 13:27:21 +0100)
>>
>> are available in the git repository at:
>>
>>    git://git.openembedded.org/meta-openembedded-contrib yzhao/4-fixes
>> http://cgit.openembedded.org/cgit.cgi/meta-openembedded-contrib/log/?h=yzhao/4-fixes
>>
>> Yi Zhao (4):
>>    debootstrap: fix host-user-contaminated
>>    espeak: fix host-user-contaminated
>>    orrery: fix host-user-contaminated
>>    logwatch: fix host-user-contaminated
>>
>>   .../debootstrap/debootstrap_1.0.67.bb              |    1 +
>>   .../recipes-extended/logwatch/logwatch_7.4.1.bb    |    1 +
>>   meta-oe/recipes-navigation/orrery/orrery_2.7.bb    |    1 +
>>   meta-oe/recipes-support/espeak/espeak_1.37.bb      |    1 +
>>   4 files changed, 4 insertions(+)
>>
>
>
>
> Kind regards,
>
> Mike Looijmans
> System Expert
>
> TOPIC Embedded Products
> Eindhovenseweg 32-C, NL-5683 KH Best
> Postbus 440, NL-5680 AK Best
> Telefoon: +31 (0) 499 33 69 79
> E-mail: mike.looijmans@topicproducts.com
> Website: www.topicproducts.com
>
> Please consider the environment before printing this e-mail
>
>
>
>
>



      reply	other threads:[~2016-01-15  7:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-14  8:19 [meta-oe][PATCH 0/4] host-user-contaminated fixes for meta-oe Yi Zhao
2016-01-14  8:19 ` [meta-oe][PATCH 1/4] debootstrap: fix host-user-contaminated Yi Zhao
2016-01-14  8:19 ` [meta-oe][PATCH 2/4] espeak: " Yi Zhao
2016-01-14  8:19 ` [meta-oe][PATCH 3/4] orrery: " Yi Zhao
2016-01-14  8:19 ` [meta-oe][PATCH 4/4] logwatch: " Yi Zhao
2016-01-14 10:21 ` [meta-oe][PATCH 0/4] host-user-contaminated fixes for meta-oe Mike Looijmans
2016-01-15  7:19   ` Yi Zhao [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=56989D73.8080303@windriver.com \
    --to=yi.zhao@windriver.com \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox