From: Kevin Hilman <khilman@baylibre.com>
To: "Bird, Timothy" <Tim.Bird@sony.com>
Cc: "fuego@lists.linuxfoundation.org" <fuego@lists.linuxfoundation.org>
Subject: Re: [Fuego] Fuego's version up and other changes
Date: Wed, 15 Feb 2017 10:39:08 -0800 [thread overview]
Message-ID: <m2poij8fjn.fsf@baylibre.com> (raw)
In-Reply-To: <ECADFF3FD767C149AD96A924E7EA6EAF104A570A@USCULXMSG01.am.sony.com> (Timothy Bird's message of "Tue, 14 Feb 2017 19:55:55 +0000")
"Bird, Timothy" <Tim.Bird@sony.com> writes:
[...]
> FYI - I have requested a dedicated BOF session at ELC for the "Status and Roadmap of Fuego".
> I'll announce the date, time and room when I hear back.
>
> I'd like to discuss the status of our different trees, and work out a plan for merging
> stuff at ELC. I'd like to get the merge done as soon after ELC as possible, to prevent further diverging.
> Jan-Simon will be at ELC as well. I believe the three of us are key drivers of Fuego
> at this point, and if we can hammer out a plan for moving forward, that would be great.
>
> Anyone else on this list going to ELC? If so, please bring your Fuego feedback and ideas
> to the BOF.
Unforunately, I won't be at ELC (first one I've missed in many years) :(
My feature request: Fuego create & submit LAVA v2 jobs and post-process results.
Kevin
next prev parent reply other threads:[~2017-02-15 18:39 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-11 0:28 [Fuego] RFC: Fuego's version up and other changes Daniel Sangorrin
2017-01-12 5:51 ` Ibe.Kengo
2017-01-12 6:44 ` Daniel Sangorrin
2017-01-12 8:15 ` Ibe.Kengo
2017-01-12 8:45 ` Daniel Sangorrin
2017-01-12 9:04 ` Ibe.Kengo
2017-01-12 9:18 ` Daniel Sangorrin
2017-01-13 1:02 ` Bird, Timothy
2017-01-13 1:29 ` Daniel Sangorrin
2017-01-13 1:37 ` Bird, Timothy
2017-01-13 1:45 ` Daniel Sangorrin
2017-01-13 1:57 ` Bird, Timothy
2017-01-13 2:05 ` Daniel Sangorrin
2017-01-13 3:34 ` Bird, Timothy
2017-01-13 4:36 ` Daniel Sangorrin
2017-01-20 0:53 ` [Fuego] " Bird, Timothy
2017-01-20 7:09 ` Daniel Sangorrin
2017-01-28 2:14 ` Bird, Timothy
2017-01-31 1:56 ` Daniel Sangorrin
2017-01-31 20:54 ` Jan-Simon Möller
2017-02-02 1:25 ` Bird, Timothy
2017-02-02 5:49 ` Daniel Sangorrin
2017-02-02 9:50 ` Jan-Simon Möller
2017-01-31 23:15 ` Jan-Simon Möller
2017-02-01 0:56 ` Daniel Sangorrin
2017-02-01 10:46 ` Jan-Simon Möller
2017-02-02 1:57 ` Bird, Timothy
2017-02-02 6:06 ` Daniel Sangorrin
2017-02-03 1:04 ` Daniel Sangorrin
2017-02-13 3:51 ` Daniel Sangorrin
2017-02-14 19:55 ` Bird, Timothy
2017-02-15 18:39 ` Kevin Hilman [this message]
2017-02-02 9:57 ` Jan-Simon Möller
2017-02-02 5:45 ` Daniel Sangorrin
2017-02-02 1:35 ` Bird, Timothy
2017-02-02 5:52 ` Daniel Sangorrin
2017-02-02 10:04 ` Jan-Simon Möller
2017-02-02 20:51 ` Kevin Hilman
2017-02-02 22:16 ` Bird, Timothy
2017-02-02 23:37 ` Kevin Hilman
2017-02-04 0:07 ` Jan-Simon Möller
2017-02-07 1:56 ` Daniel Sangorrin
2017-02-02 1:17 ` Bird, Timothy
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=m2poij8fjn.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=Tim.Bird@sony.com \
--cc=fuego@lists.linuxfoundation.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.