From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Rich Persaud <persaur@gmail.com>
Cc: meta-virtualization@yoctoproject.org
Subject: Re: [PATCH V2 1/3] sanity-bbappend.bbclass: add class for bbappend files checking
Date: Mon, 25 Sep 2017 13:45:11 +0100 [thread overview]
Message-ID: <1506343511.31732.22.camel@linuxfoundation.org> (raw)
In-Reply-To: <8C5544EC-5FF6-434A-8589-62C3DF47867F@gmail.com>
On Mon, 2017-09-25 at 08:00 -0400, Rich Persaud wrote:
> On Sep 25, 2017, at 06:40, Richard Purdie <richard.purdie@linuxfounda
> tion.org> wrote:
> ...
> >
> > So yes, I think there is a valid issue here and in many senses, YP
> > Compat v2 is probably highlighting a real problem but I suspect
> > this
> > patch series is not the way to fix it...
> Are there docs on YP Compat v2? A web search turned up this RFC:
>
> https://lists.yoctoproject.org/pipermail/yocto/2017-February/034489.h
> tml
There is the yocto-layer-check script which basically embodies the
planned changes. I do need to write up a lot of the information but am
struggling to find the time to do that the justice it needs...
Cheers,
Richard
next prev parent reply other threads:[~2017-09-25 12:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 8:41 [PATCH V2 1/3] sanity-bbappend.bbclass: add class for bbappend files checking Chen Qi
2017-09-25 8:41 ` [PATCH V2 2/3] linux-yocto: make bbappend have effect conditionally Chen Qi
2017-09-25 8:41 ` [PATCH V2 3/3] README: update to include information about bbappend inclusion Chen Qi
2017-09-25 10:40 ` [PATCH V2 1/3] sanity-bbappend.bbclass: add class for bbappend files checking Richard Purdie
2017-09-25 12:00 ` Rich Persaud
2017-09-25 12:45 ` Richard Purdie [this message]
2017-09-25 12:49 ` Bruce Ashfield
2017-09-25 13:10 ` Richard Purdie
2017-09-25 14:02 ` Bruce Ashfield
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=1506343511.31732.22.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=meta-virtualization@yoctoproject.org \
--cc=persaur@gmail.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.