Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: bavery <brian.avery@intel.com>
To: bitbake-devel@lists.openembedded.org
Cc: bavery <brian.avery@intel.com>,
	Belen Barros Pena <belen.barros.pena@linux.intel.com>
Subject: [PATCH 0/3] toaster: UI fixes
Date: Sun, 18 Sep 2016 19:33:12 -0700	[thread overview]
Message-ID: <cover.1474252113.git.brian.avery@intel.com> (raw)

This contains a set of UI fixes for bugs:
9832 - fix task links
9862 - fix left navigationactive item in build history pages
10037- remove duplicate layer info in cutsom recipes detail page

-b

The following changes since commit ead7c4bc8024fb4325b124dc0b663c86c4363122:

  toaster: unlock BuildEnvirnoment when build is done (2016-09-16 17:24:09 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib bavery/submit/toaster/belen/sep-18-ui
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/submit/toaster/belen/sep-18-ui

Belen Barros Pena (3):
  toaster: Fix links to tasks with specific outcome
  toaster: Indicate active navigation element
  toaster: Remove duplicate layer information

 lib/toaster/toastergui/templates/basebuildpage.html  | 7 +++++--
 lib/toaster/toastergui/templates/builddashboard.html | 6 +++---
 lib/toaster/toastergui/templates/customrecipe.html   | 2 --
 3 files changed, 8 insertions(+), 7 deletions(-)

--
1.9.1


             reply	other threads:[~2016-09-19  2:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-19  2:33 bavery [this message]
2016-09-19  2:33 ` [PATCH 1/3] toaster: Fix links to tasks with specific outcome bavery
2016-09-19  2:33 ` [PATCH 2/3] toaster: Indicate active navigation element bavery
2016-09-19  2:33 ` [PATCH 3/3] toaster: Remove duplicate layer information bavery

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=cover.1474252113.git.brian.avery@intel.com \
    --to=brian.avery@intel.com \
    --cc=belen.barros.pena@linux.intel.com \
    --cc=bitbake-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