From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2013-01-28
Date: Tue, 29 Jan 2013 20:59:56 +0100 [thread overview]
Message-ID: <20130129205956.5488353e@skate> (raw)
In-Reply-To: <CAKcgs2zMQeybp4TA+6nJ8tTdfb173S+u6Fwd8jCrEw_USv5f=w@mail.gmail.com>
Dear Gilles Talis,
On Tue, 29 Jan 2013 11:46:08 -0800, Gilles Talis wrote:
> Thanks a lot for this clear explanation. This answer my questions.
> Process seems fair enough to me. My only question for the moment
> would be how do we make sure two (or more) people are not working on
> fixing the same issue? If I want to fix a specific failure, should I
> send an email to everyone saying "hey, I am working on build failure
> X"? What is the usual process here?
As I said there is no formal process. Many build fixes are quite simple
to fix, so we just fix it and send a patch, that's it. Since the fix is
quick enough to do, there isn't a very big chance that someone else is
working on it.
For more complex cases, we send an e-mail, typically in reply to the
autobuilder e-mail, quoting the relevant build failure, and saying that
we're working on it.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-01-29 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 7:34 [Buildroot] [autobuild.buildroot.net] Build results for 2013-01-28 Thomas Petazzoni
2013-01-29 19:30 ` Gilles Talis
2013-01-29 19:39 ` Thomas Petazzoni
2013-01-29 19:46 ` Gilles Talis
2013-01-29 19:59 ` Thomas Petazzoni [this message]
2013-01-29 20:16 ` Gilles Talis
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=20130129205956.5488353e@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