From: "Bird, Timothy" <Tim.Bird@sony.com>
To: Rafael Gago Castano <RGC@hms.se>
Cc: "fuego@lists.linuxfoundation.org" <fuego@lists.linuxfoundation.org>
Subject: Re: [Fuego] First steps with fuego
Date: Wed, 17 May 2017 15:33:57 +0000 [thread overview]
Message-ID: <ECADFF3FD767C149AD96A924E7EA6EAF1FA89062@USCULXMSG01.am.sony.com> (raw)
In-Reply-To: <HE1PR06MB303664977354933E138C5F7DC2E70@HE1PR06MB3036.eurprd06.prod.outlook.com>
> -----Original Message-----
> From: Rafael Gago Castano on Tuesday, May 16, 2017 11:36 PM
> Thank you for the help and references. I'll check that.
>
> Tomorrow I will show my findings on a meeting and it will be decided if we go
> forward and invest more in Fuego with the objective of replacing our working
> LAVA setup in the future. I hope to go forward with this. If we don't at least
> I'll try to provide feedback about what the others thought.
Thanks very much! Even if you decide to stick with LAVA, getting feedback on
what Fuego is missing, or could improve, is very helpful.
-- Tim
next prev parent reply other threads:[~2017-05-17 15:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 9:49 [Fuego] First steps with fuego Rafael Gago Castano
2017-05-09 19:04 ` Bird, Timothy
2017-05-10 6:32 ` Rafael Gago Castano
2017-05-10 13:12 ` Rafael Gago Castano
2017-05-10 19:30 ` Bird, Timothy
[not found] ` <HE1PR06MB3036959D51FD5FBFC02208C8C2ED0@HE1PR06MB3036.eurprd06.prod.outlook.com>
[not found] ` <ECADFF3FD767C149AD96A924E7EA6EAF1FA88A98@USCULXMSG01.am.sony.com>
2017-05-12 9:38 ` Rafael Gago Castano
2017-05-12 18:05 ` Bird, Timothy
2017-05-15 8:21 ` Rafael Gago Castano
2017-05-12 14:33 ` Rafael Gago Castano
2017-05-12 18:39 ` Bird, Timothy
2017-05-15 13:57 ` Rafael Gago Castano
2017-05-15 22:37 ` Bird, Timothy
2017-05-16 14:38 ` Rafael Gago Castano
2017-05-17 5:06 ` Bird, Timothy
2017-05-17 6:35 ` Rafael Gago Castano
2017-05-17 15:33 ` Bird, Timothy [this message]
2017-05-22 8:23 ` Rafael Gago Castano
2017-05-22 20:51 ` 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=ECADFF3FD767C149AD96A924E7EA6EAF1FA89062@USCULXMSG01.am.sony.com \
--to=tim.bird@sony.com \
--cc=RGC@hms.se \
--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.