From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] New contact for ARC support in Buildroot
Date: Sat, 1 Feb 2014 08:40:53 +0100 [thread overview]
Message-ID: <20140201084053.3d9c0903@skate> (raw)
In-Reply-To: <E6BF041E97966E4DB955F0DF883AD2D685F4084F@de02wembxa.internal.synopsys.com>
Dear Mischa Jonker,
On Fri, 31 Jan 2014 15:17:57 +0000, Mischa Jonker wrote:
> I would like to introduce you to Anton, who will take over my duties as primary contact for ARC support in Buildroot. If there are questions regarding the ARC toolchain and its integration in Buildroot, Anton will be happy to answer them.
Welcome Anton!
However, you forgot to Cc Anton, so we don't know (yet) what his e-mail
address his.
Also, should the daily e-mail with the ARC autobuilder failures now be
sent to Anton? Or to both Anton and you?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-01 7:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-31 15:17 [Buildroot] New contact for ARC support in Buildroot Mischa Jonker
2014-02-01 7:40 ` Thomas Petazzoni [this message]
2014-02-03 8:46 ` Anton Kolesov
2014-02-03 17:29 ` Thomas Petazzoni
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=20140201084053.3d9c0903@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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