[Buildroot] misc development news

Thiago A. Corrêa thiago.correa at gmail.com
Wed Apr 29 21:17:12 UTC 2009

On Wed, Apr 29, 2009 at 6:00 PM, Markus Heidelberg
<markus.heidelberg at web.de> wrote:
> Thiago A. Corrêa, 29.04.2009:
>> 2009/4/28 Peter Korsgaard <jacmet at uclibc.org>:
>> > In fact I would like us to move to a workflow where all changes are
>> > first posted to the list before committing to the official tree,
>> > similar to how it's handled in the Linux kernel, U-Boot,  ..
>> I don't see that working. It does for the linux kernel because of the
>> size of it's contributor base, we are greatly under powered for this
>> scheme. Patches would just get a big backlog for you to handle and we
>> would be unable to help.
>> I think the current commit first review later works best in our case.
>> We don't quite have enough ppl reviewing changes and reverting a patch
>> has been uncommon, yet, it's not that hard when necessary.
> Peter seems to review many commits and fixes them or asks the committers
> to fix them. So maybe the work isn't really less nowadays, but I'm not
> sure.

Indeed unfortunally I don't offer as much help as I would like to, but
at least I don't get in the way *smile*
Imagine that on top of that, he would have to commit your patches, my
patches, etc.
It does look like it is work to do the same job.

If we don't sort out how we are going to work, this move could just
send ppl away, frustrated because we can't get things done.
I for one am still clueless on how should I continue to contribute,
and yet I'm afraid that I will have to keep track of several different
trees, on top of the 2 I already have (My private development +
upstream buildroot).

More information about the buildroot mailing list