[Buildroot] [uclinux-dist-devel] [Announcement] The 2012R2 buildroot Linux release for Blackfin

Thomas De Schampheleire patrickdepinguin+buildroot at gmail.com
Fri Mar 8 14:52:12 UTC 2013


Hi,

On Fri, Mar 8, 2013 at 9:33 AM, Thomas Petazzoni
<thomas.petazzoni at free-electrons.com> wrote:
> Dear Zhang, Sonic,
>
> On Fri, 8 Mar 2013 02:19:01 -0500, Zhang, Sonic wrote:
>
>> I mean my new patches to address some of your feedbacks in former patches got no response.
>> http://lists.busybox.net/pipermail/buildroot/2012-August/057505.html
>> http://lists.busybox.net/pipermail/buildroot/2012-August/057506.html
>> http://lists.busybox.net/pipermail/buildroot/2012-August/057668.html
>> http://lists.busybox.net/pipermail/buildroot/2012-August/057669.html
>
> Yes, just like with any project, it is not easy to get core changes
> merged, especially when those are the first contributions from a
> developer. It requires time, patience and perseverance.
>
> That's also why I was proposing you to get started with all the package
> changes first. They are a lot easier to handle, less intrusive, and
> therefore easier to get merged.

I fully agree with Thomas P. that integrating the Blackfin changes
into mainline buildroot would be beneficial for both the buildroot as
the Blackfin community. As Thomas indicated, the buildroot community
is now more alive than ever, and I'm sure that a new series of
buildroot patches from the Blackfin community will not go unnoticed,
especially now that you're in the middle of our radar ;-)

I also agree with the approach Thomas suggests: let's start with the
simple patches like package changes. This will reduce the divergence
between both trees without too much effort, after which we can tackle
the bigger stuff.

What do you think?

By the way: I don't see Sonic's replies appearing on the buildroot
mailing list. Is it possible to keep that list in copy?

Best regards,
Thomas


More information about the buildroot mailing list