From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Microblaze maintenance in Buildroot
Date: Sun, 6 Apr 2014 19:29:08 +0200 [thread overview]
Message-ID: <20140406192908.6340fa8b@skate> (raw)
In-Reply-To: <CAEBucnA77jfvsGsgikuc=J_WyC1d98G_KaWqXbqUEW4YqurtHg@mail.gmail.com>
Dear Spenser Gilliland,
On Sun, 6 Apr 2014 12:22:58 -0500, Spenser Gilliland wrote:
> Very sorry about this. I am currently overloaded with other
> responsibilities. Hopefully, someone else can pick this up.
No problem at all. The intention of my e-mail was not in any way to
blame anyone for not doing some work: we all know that most of the
Buildroot contribution is done on a volunteer-basis.
However, it is part of handling a volunteer-driver project to make sure
that features get maintained/supported even if some of the volunteers
are not available.
Thanks! :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-04-06 17:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-06 13:42 [Buildroot] Microblaze maintenance in Buildroot Thomas Petazzoni
2014-04-06 17:22 ` Spenser Gilliland
2014-04-06 17:29 ` Thomas Petazzoni [this message]
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=20140406192908.6340fa8b@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 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.