From: Michael Wood <michael.g.wood@intel.com>
To: toaster@yoctoproject.org
Subject: Re: [review-request] adamian/20150727_tables
Date: Tue, 28 Jul 2015 11:50:23 +0100 [thread overview]
Message-ID: <55B75E6F.7090301@intel.com> (raw)
In-Reply-To: <D1DD1A36.60D28%belen.barros.pena@intel.com>
On 28/07/15 11:40, Barros Pena, Belen wrote:
>
> On 27/07/2015 17:43, "toaster-bounces@yoctoproject.org on behalf of
> Damian, Alexandru" <toaster-bounces@yoctoproject.org on behalf of
> alexandru.damian@intel.com> wrote:
>
>> Hi,
>>
>>
>> This patch removes duplicates in the project compatible layers tables.
>>
>>
>> In effect, this patch computes, for each entry, its equivalence class in
>> the project context (based on the current project release), and selects
>> only the class leaders - the entries with the highest
>> priority in their own equivalence class.
>>
>>
>> This patch is important because the QuerySet here is the same one as one
>> would use to populate the future ProjectAvailableLayers table.
>>
Wouldn't this be better in orm.project.compatible_layerversions ?
So that anyone using that function will no longer get duplicated entries.
>>
>> Please review and merge:
>>
>>
>> http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=adamian/201
>> 50727_tables
> From the outside this seems to work. I now get only one openembedded-core
> layer, with revision matching the project release, which makes sense to
> me.
>
> Thanks
>
> Belén
>
>>
>> Cheers,
>>
>> Alex
>>
>>
>> --
>> Alex Damian
>> Yocto Project
>>
>> SSG / OTC
>>
>>
>>
next prev parent reply other threads:[~2015-07-28 10:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 16:43 [review-request] adamian/20150727_tables Damian, Alexandru
2015-07-28 10:40 ` Barros Pena, Belen
2015-07-28 10:50 ` Michael Wood [this message]
2015-07-28 13:15 ` Damian, Alexandru
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=55B75E6F.7090301@intel.com \
--to=michael.g.wood@intel.com \
--cc=toaster@yoctoproject.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 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.