All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: "Barros Pena, Belen" <belen.barros.pena@intel.com>
Cc: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: [PATCH 0/7] Fix 8004
Date: Thu, 1 Oct 2015 16:03:08 +0300	[thread overview]
Message-ID: <20151001130308.GA30689@linux.intel.com> (raw)
In-Reply-To: <D232BD52.66849%belen.barros.pena@intel.com>

Hi Belen,

On Thu, Oct 01, 2015 at 09:39:33AM +0000, Barros Pena, Belen wrote:

> This seems to be working, except for a small issue: the second-level
> dependency information is not showing up in the layer details page. So,
> for example, if you look at meta-aurora in the compatible layers table,
> you get 6 dependencies listed. If you add meta-aurora to your project, you
> also get 6 dependencies listed in the dependencies modal dialog. But if
> you click meta-aurora and check the layer details page, there are only 4
> dependencies listed. We need to show the second-level dependency
> information in the layer details page too.

Thank you for pointing out to this. I'll fix it in v2.

--
Regards,
Ed


      reply	other threads:[~2015-10-01 13:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 12:02 [PATCH 0/7] Fix 8004 Ed Bartosh
2015-09-30 12:02 ` [PATCH 1/7] toaster: implement API to get full list of deps Ed Bartosh
2015-09-30 12:02 ` [PATCH 2/7] toaster: use get_alldeps in layerdetails renderer Ed Bartosh
2015-09-30 12:02 ` [PATCH 3/7] toaster: add template filter get_alldeps Ed Bartosh
2015-09-30 12:02 ` [PATCH 4/7] toaster: use get_alldeps in LayerTable Ed Bartosh
2015-09-30 12:02 ` [PATCH 5/7] toaster: fix NameError Ed Bartosh
2015-09-30 12:02 ` [PATCH 6/7] toaster: fix orm tests Ed Bartosh
2015-09-30 12:02 ` [PATCH 7/7] toaster: test get_alldeps API Ed Bartosh
2015-10-01  9:39 ` [PATCH 0/7] Fix 8004 Barros Pena, Belen
2015-10-01 13:03   ` Ed Bartosh [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=20151001130308.GA30689@linux.intel.com \
    --to=ed.bartosh@linux.intel.com \
    --cc=belen.barros.pena@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.