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:32:02 +0100 [thread overview]
Message-ID: <4F22C372.20908@visionsystems.de> (raw)
In-Reply-To: <20120127162722.7c227e2f@skate>
Am 27.01.2012 16:27, schrieb Thomas Petazzoni:
> Le Fri, 27 Jan 2012 16:24:27 +0100,
> Peter Korsgaard <jacmet@uclibc.org> a ?crit :
>
>> Completely FIFO is not an option with the current backlog as updates
>> are sometimes sent and the latest version should be used, but I agree
>> - The situation is not optimal.
>
> Yeah, of course full FIFO will not work. I just wanted to point out
> some of the patch sets that have been sitting around for a while. But
> agreed, the most recent patches are the one that have the highest
> chance of applying properly, so it's definitely easier to handle them.
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.
Best regards,
Yegor
next prev parent reply other threads:[~2012-01-27 15:32 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 [this message]
2012-01-27 15:36 ` Thomas Petazzoni
2012-01-27 15:50 ` Yegor Yefremov
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=4F22C372.20908@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