From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Call for autobuild fixing for 2013.11
Date: Tue, 26 Nov 2013 14:26:16 +0100 [thread overview]
Message-ID: <20131126142616.64719ad6@skate> (raw)
In-Reply-To: <CAAXf6LU1_ybwfA9DGfkq7fGJ17LU5k4cQb=G14rg6oSdNY=WAg@mail.gmail.com>
Dear Thomas De Schampheleire,
On Sat, 23 Nov 2013 13:56:28 +0100, Thomas De Schampheleire wrote:
> > If you want to fix a particular problem but get stuck, don't
> > hesitate in sending your findings to the list. Other developers can
> > try to help you.
>
> It's great to see several people sending patches that fix autobuild
> failures! Let's keep up this work until the end of the month, when
> 2013.11 is released...
Yes, we've made really good progress here, and it's indeed great to see
that more people have decided to the play the "let's fix autobuilder
failures" game :-)
However, I would not say that this effort should stop at the end of the
month, when 2013.11 is released. When 2013.11 is released, next will be
merged in master, and we'll have a nice set of new autobuilder failures
to look at, not to mention the existing ones that haven't been fixed
yet!
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-26 13:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-14 11:24 [Buildroot] Call for autobuild fixing for 2013.11 Thomas De Schampheleire
2013-11-14 12:35 ` [Buildroot] autobuild.b.o down Thomas Petazzoni
2013-11-17 8:32 ` [Buildroot] Call for autobuild fixing for 2013.11 Thomas De Schampheleire
2013-11-23 12:56 ` Thomas De Schampheleire
2013-11-26 13:26 ` Thomas Petazzoni [this message]
2013-12-02 11:11 ` Thomas De Schampheleire
2013-12-02 12:32 ` Thomas Petazzoni
2013-12-02 12:53 ` Thomas De Schampheleire
2013-12-02 13:10 ` Thomas Petazzoni
2013-12-02 14:15 ` Thomas De Schampheleire
2013-12-02 14:39 ` Ryan Barnett
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=20131126142616.64719ad6@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