Re: [Buildroot] [PATCH v2 01/77] Remove mender packages

[Thomas Petazzoni via buildroot <buildroot@buildroot.org>]

Hello Adam,

On Mon, Sep 21, 2026 at 08:04:10PM +0200, Adam Duskett wrote:

>     Thanks for your feedback. Based on how you phrase your feedback, it
>     seems like you're somehow taking it personally, as if it was
>     specifically your contributions that were being ignored.
> 
> Nope. Other patches not from me such as the qmake QT6 series is also ignored. 

Indeed, that's a global problem and there is nothing personal about
you or your contributions.

>     While I understand the frustration that it may cause, simply being
>     "grumpy" is not going to help in any way. What would help is having
>     more contributors involved in the review of patches from others.
> 
> Don't be condescending.  This is the same line that has been used for over a
> decade. Reviews are also ignored and maintainers insist on nit picking every
> single patch. 

Please do not over-interpret my words: keep in mind that I am not a
native speaker, and in this sort of complex written conversation, it
is difficult to convey my exact state of mind. I am not condescending
at all.

>     Can I ask that rather than just looking at your own patches for your
>     own specific topic, you take a look at the bigger picture, hopefully
>     turning your "grumpiness" into more productive help/participation to
>     the Buildroot community? This is going to be a LOT more useful.
> 
> Again, don't be condescending. I was CCed on a patch series, I put in my two
> cents. If my opinion wasn't wanted then don't include me on the email. 

Your opinion is wanted.

>     And I restate: Mender is an important piece of software of the
>     embedded Linux ecosystem, and it makes complete sense to have good
>     support for it in upstream Buildroot.
> 
> Then perhaps one of the maintainers can step up and update the package? I
> wasn't being "grumpy" as you put it when I said an external tree is easier for
> me to maintain. I choose not to deal with the endless nitpicking fand
> bikeshedding rom the maintainers, as I have voiced my frustrations with the
> maintainers and developers for more than a decade and nothing has changed. 

We are not bikeshedding, we are ensuring a proper consistency and
quality level. Just like what happens in every open-source project
that is properly maintained.

Before Peter Korsgaard took over the maintenance of Buildroot in
2008-2009, multiple people not coordinating with each other and not
having a solid idea of how things should be done had commit
access. And trust me, the result was atrocious. Every problem was
solved in a different way in different places, the code had no
consistency. It was very very difficult to work with. So what you
(hopefully?) like in Buildroot today is in large part due to what you
call "endless nitpicking and bikeshedding from the maintainers".

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot