From: Yegor Yefremov <yegor_sub1@visionsystems.de>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot Developer Day, Friday 3rd February, Brussels
Date: Fri, 27 Jan 2012 16:50:59 +0100 [thread overview]
Message-ID: <4F22C7E3.30900@visionsystems.de> (raw)
In-Reply-To: <20120127163630.5d604b7d@skate>
Am 27.01.2012 16:36, schrieb Thomas Petazzoni:
> Le Fri, 27 Jan 2012 16:32:02 +0100,
> Yegor Yefremov <yegor_sub1@visionsystems.de> a ?crit :
>
>> That's where such tools as gerrit and build server come in play,
>> cause they perform automatic integration build and let you know if
>> patch is broken or breaks something.
> Unfortunately, it doesn't work this way with Buildroot. There is no
> such thing as "the build works" or "the build doesn't work" as in a
> regular software. Depending on what the patch modifies, a different set
> of configuration options needs to be set in order to test that the patch
> actually works. With regular software, you can easily test build a few
> configuration options (debug vs. release mode, support of this or
> support of that), but Buildroot has millions of different possibles
> combinations, which your build server cannot test within a reasonable
> time. So only an human being can decide "Hmm, for this patch, I will
> try out this config and this config and this config, because those
> configs are the one that will make actual use of the patch".
I see your point. So the only useful features were:
1. keeping all patches at one place
2. automatic checks for applying patches (not building)
Yegor
next prev parent reply other threads:[~2012-01-27 15:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-23 23:08 [Buildroot] Buildroot Developer Day, Friday 3rd February, Brussels Thomas Petazzoni
2012-01-24 9:56 ` Thomas Petazzoni
2012-01-25 11:03 ` Thomas De Schampheleire
2012-01-25 12:57 ` Thomas Petazzoni
2012-01-25 18:04 ` Michael S. Zick
2012-01-25 18:07 ` Michael S. Zick
2012-01-27 10:33 ` Arnout Vandecappelle
2012-01-27 11:58 ` Thomas Petazzoni
2012-01-27 15:24 ` Peter Korsgaard
2012-01-27 15:27 ` Thomas Petazzoni
2012-01-27 15:32 ` Yegor Yefremov
2012-01-27 15:36 ` Thomas Petazzoni
2012-01-27 15:50 ` Yegor Yefremov [this message]
2012-01-27 15:52 ` Thomas Petazzoni
2012-01-27 19:36 ` Peter Korsgaard
2012-01-30 9:19 ` Thomas De Schampheleire
2012-01-30 9:42 ` Peter Korsgaard
2012-01-30 14:16 ` Thomas De Schampheleire
2012-01-30 15:09 ` Peter Korsgaard
2012-01-30 11:26 ` Thomas Petazzoni
2012-01-29 15:46 ` Luca Ceresoli
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=4F22C7E3.30900@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--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