All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jolley, Stephen K" <stephen.k.jolley@intel.com>
To: "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Cc: "Avery, Brian" <brian.avery@intel.com>,
	"Dumitru, Alin" <alin.dumitru@intel.com>
Subject: Reminder: Toaster Weekly Meeting
Date: Wed, 20 Apr 2016 05:02:18 +0000	[thread overview]
Message-ID: <9ADD3FDE8B189B4AA2F8A3C711F8155E570F5DCB@fmsmsx111.amr.corp.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 724 bytes --]

Join the weekly call for Toaster contributors.
Wednesday, April 20, 2016 8:00 AM US Pacific Time

Call Details:
Tel: 1-888-875-9370/916-356-2663
Bridge: 4
Passcode: 1434913


AR's:

AR: Libby: Disposition 9453. (Done)


Agenda:
Team Member Updates:
Triage Toaster bugs: https://wiki.yoctoproject.org/wiki/Bug_Triage#YP_Toaster_and_Layer_Index_Bugs_needing_Triage
Discuss YP 2.2 Planning:
AR Review's:
Opens:

Thanks,

Stephen K. Jolley
Yocto Project Program Manager
INTEL, MS JF1-255, 2111 N.E. 25th Avenue, Hillsboro, OR 97124
*   Work Telephone:          (503) 712-0534
*    Cell:                                (208) 244-4460
* Email:                             stephen.k.jolley@intel.com


[-- Attachment #2: Type: text/html, Size: 11396 bytes --]

             reply	other threads:[~2016-04-20  5:02 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20  5:02 Jolley, Stephen K [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-10-25 20:37 Reminder: Toaster Weekly Meeting Jolley, Stephen K
2016-10-04 19:37 Jolley, Stephen K
2016-09-27 19:02 Jolley, Stephen K
2016-09-28  6:19 ` Cruz, Libertad
2016-09-21  5:21 Jolley, Stephen K
2016-09-14  3:46 Jolley, Stephen K
2016-09-07  3:42 Jolley, Stephen K
2016-08-31  3:40 Brian Avery
2016-08-23 15:40 Barros Pena, Belen
2016-08-17  5:07 Brian Avery
2016-08-10  3:01 Brian Avery
2016-08-02 21:38 Brian Avery
2016-07-26 23:41 Brian Avery
2016-07-27  0:01 ` Brian Avery
2016-07-19 23:51 Brian Avery
2016-07-20 13:14 ` Smith, Elliot
2016-07-12 18:39 Brian Avery
2016-07-06  5:12 Brian Avery
2016-06-29  4:17 Jolley, Stephen K
2016-06-21 22:27 Jolley, Stephen K
2016-06-15  4:05 Jolley, Stephen K
2016-06-08  0:02 Jolley, Stephen K
2016-06-01  1:16 Jolley, Stephen K
2016-05-25  3:32 Jolley, Stephen K
2016-05-18  4:38 Jolley, Stephen K
2016-05-11  3:13 Jolley, Stephen K
2016-05-03 23:09 Jolley, Stephen K
2016-04-27  2:56 Jolley, Stephen K
2016-04-13  1:02 Jolley, Stephen K
2016-04-05 23:33 Jolley, Stephen K
2016-04-06 11:47 ` sujith h
2016-03-30  4:34 Jolley, Stephen K
2016-03-23  4:14 Jolley, Stephen K
2016-03-15 22:04 Jolley, Stephen K
2016-03-09  0:32 Jolley, Stephen K
2016-03-09 14:03 ` sujith h
2016-03-02 11:05 Barros Pena, Belen
2016-02-24  9:17 Barros Pena, Belen
2016-02-17  4:22 Jolley, Stephen K
2016-02-10  7:12 Jolley, Stephen K
2016-02-02 22:32 Jolley, Stephen K
2016-01-27  6:23 Jolley, Stephen K
2016-01-19 23:23 Jolley, Stephen K
2016-01-13  1:25 Jolley, Stephen K
2016-01-06  2:56 Jolley, Stephen K
2015-12-16  2:19 Jolley, Stephen K
2015-12-09  2:25 Jolley, Stephen K
2015-12-02  3:20 Jolley, Stephen K
2015-11-25  3:36 Jolley, Stephen K
2015-11-18  6:39 Jolley, Stephen K
2015-11-10 23:41 Jolley, Stephen K
2015-11-04  0:13 Jolley, Stephen K
2015-10-28  4:31 Jolley, Stephen K
2015-10-20 23:00 Jolley, Stephen K
2015-10-13 21:12 Jolley, Stephen K
2015-10-06 22:20 Jolley, Stephen K
2015-09-30  4:46 Jolley, Stephen K
2015-09-23  9:15 Barros Pena, Belen
2015-09-23 10:47 ` Barros Pena, Belen
2015-09-22 21:22 Jolley, Stephen K
2015-09-16  2:44 Jolley, Stephen K
2015-09-08 21:24 Jolley, Stephen K
2015-09-02 10:10 Barros Pena, Belen
2015-09-01 22:00 Jolley, Stephen K
2015-08-25 21:26 Jolley, Stephen K
2015-08-19  5:14 Jolley, Stephen K
2015-08-12 14:26 Barros Pena, Belen
2015-08-11 21:59 Jolley, Stephen K
2015-08-05  9:42 Barros Pena, Belen
2015-08-04 21:14 Jolley, Stephen K
2015-07-28 21:09 Jolley, Stephen K
2015-07-29 10:03 ` Damian, Alexandru
2015-07-29 10:46   ` 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=9ADD3FDE8B189B4AA2F8A3C711F8155E570F5DCB@fmsmsx111.amr.corp.intel.com \
    --to=stephen.k.jolley@intel.com \
    --cc=alin.dumitru@intel.com \
    --cc=brian.avery@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.