From: "Aníbal Limón" <anibal.limon@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
"Flanagan, Elizabeth" <elizabeth.flanagan@intel.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/4] license_class: Added support for LICENSE_PRIORITY in manifest creation
Date: Fri, 27 Feb 2015 10:27:15 -0600 [thread overview]
Message-ID: <54F09AE3.5030701@linux.intel.com> (raw)
In-Reply-To: <1424973056.26813.34.camel@linuxfoundation.org>
HI Richard,
I can do the rebase this change affects documentation that needs to
describe LICENSE_PRIORITY feature.
Kind regards,
alimon
On 26/02/15 11:50, Richard Purdie wrote:
> On Thu, 2015-02-26 at 16:34 +0000, Flanagan, Elizabeth wrote:
>> Actually, this contains almost exactly what I was writing. So yes, I
>> ACKing.
> Can someone post a rebased patch of what we're looking to merge please?
>
> Cheers,
>
> Richard
>
>
next prev parent reply other threads:[~2015-02-27 16:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 18:34 [PATCH 0/4] license_class: Added support for LICENSE_PRIORITY in manifest creation Aníbal Limón
2014-10-29 18:34 ` [PATCH 1/4] license_class: Reimplemented manifest creation in python Aníbal Limón
2014-10-29 21:28 ` Richard Purdie
2014-10-30 23:08 ` Aníbal Limón
2014-10-29 18:34 ` [PATCH 2/4] license_class: Added support for INCOMPATIBLE_LICENSE into license_create_manifest Aníbal Limón
2014-10-29 18:34 ` [PATCH 3/4] license_class: Added LICENSE_PRIORITY support Aníbal Limón
2014-10-29 18:34 ` [PATCH 4/4] license_class: Fix remove + trim in license_create_manifest Aníbal Limón
2015-02-24 16:00 ` [PATCH 0/4] license_class: Added support for LICENSE_PRIORITY in manifest creation Paul Eggleton
2015-02-24 16:05 ` Aníbal Limón
2015-02-24 17:08 ` Flanagan, Elizabeth
2015-02-26 16:34 ` Flanagan, Elizabeth
2015-02-26 17:50 ` Richard Purdie
2015-02-27 16:27 ` Aníbal Limón [this message]
2015-02-27 16:31 ` Paul Eggleton
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=54F09AE3.5030701@linux.intel.com \
--to=anibal.limon@linux.intel.com \
--cc=elizabeth.flanagan@intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=richard.purdie@linuxfoundation.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