All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Reyna, David" <david.reyna@windriver.com>
To: "BARROS PENA, BELEN" <belen.barros.pena@intel.com>,
	"toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: Breadcrumb changes (YB6587)
Date: Wed, 24 Sep 2014 08:29:00 +0000	[thread overview]
Message-ID: <5E53D14CE4667A45B9A06760DE5D13D05CDF2B2A@ALA-MBB.corp.ad.wrs.com> (raw)
In-Reply-To: <D046089A.4A3B4%belen.barros.pena@intel.com>

Hi Belén,

Just one question. 

This makes sense for builds that are under a project, but what about regular builds that a built outside of a project? 

Will there be a catch-all project name for the "wild" builds, or are there two cases for breadcrumbs, this new way for builds with projects and the original way for regular builds?

I ask because while in non-managed mode you cannot see projects, but in managed mode you can see both project and non-project builds.

Thanks,
David

> -----Original Message-----
> From: toaster-bounces@yoctoproject.org [mailto:toaster-
> bounces@yoctoproject.org] On Behalf Of Barros Pena, Belen
> Sent: Monday, September 22, 2014 9:11 AM
> To: toaster@yoctoproject.org
> Subject: [Toaster] Breadcrumb changes (YB6587)
> 
> Adding projects to Toaster means some changes to the Toaster structure and
> the way we identify builds. Those changes impact the breadcrumb we show in
> most Toaster pages.
> 
> A description of the changes needed is here
> 
> https://bugzilla.yoctoproject.org/attachment.cgi?id=2135
> 
> Belén
> 
> 
> --
> _______________________________________________
> toaster mailing list
> toaster@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/toaster


  reply	other threads:[~2014-09-24  8:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 16:10 Breadcrumb changes (YB6587) Barros Pena, Belen
2014-09-24  8:29 ` Reyna, David [this message]
2014-09-24  9:25   ` Barros Pena, Belen
2014-09-30 10:14     ` 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=5E53D14CE4667A45B9A06760DE5D13D05CDF2B2A@ALA-MBB.corp.ad.wrs.com \
    --to=david.reyna@windriver.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.