From: agustin.benito@codethink.co.uk (Agustin Benito Bethencourt)
To: cip-dev@lists.cip-project.org
Subject: [cip-dev] About B@D release, Renesas support and project-x
Date: Mon, 2 Oct 2017 16:14:23 +0200 [thread overview]
Message-ID: <59D249BF.1020004@codethink.co.uk> (raw)
Hi Daniel,
since you and Robert are doing activities that are related and need to
be done by ELCE, maybe it would be good to have a sync meeting to plan
them. I assume your request today at the TSC meeting goes in that direction.
We usually meet on Thursdays but since Robert might need some time for
"landing" it might be better to have a video chat (or a call) on Friday.
Maybe Chris and others want to join.
* What do you think?
* Which channel would you prefer?
* Which time slot have you available, considering the timezone difference?
It would be a meeting for planning the technical tasks up to ELCE.
Best Regards
--
Agustin Benito Bethencourt
Principal Consultant - FOSS at Codethink
agustin.benito at codethink.co.uk
next reply other threads:[~2017-10-02 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 14:14 Agustin Benito Bethencourt [this message]
2017-10-02 14:56 ` [cip-dev] About B@D release, Renesas support and project-x Chris Paterson
2017-10-04 7:04 ` Daniel Sangorrin
2017-10-04 9:01 ` Agustin Benito Bethencourt
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=59D249BF.1020004@codethink.co.uk \
--to=agustin.benito@codethink.co.uk \
--cc=cip-dev@lists.cip-project.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