[Buildroot] Worried about patches not being merged?

Thomas Petazzoni thomas.petazzoni at free-electrons.com
Fri Mar 20 16:02:29 UTC 2015


On Thu, 19 Mar 2015 23:27:22 +0100, Angelo Compagnucci wrote:

> I have more or less done, I think in the WE I can push a patch to have
> tags attached to patches.

Awesome. Another thing that would be great in the long term is to make
the patchwork UI a bit reactive (Ajax stuff, etc.).

> > Ah, really? Could you describe a bit the workflow / how it would work ?
> I have to find more time to elaborate if that software could be bended
> to buildroot needs. I have only a superficially view right now. I
> promise to look better at it.

Ok, thanks.

> > Well, is there really such a huge pile of new packages / medium level
> > patches / newbie patches ? We tend to apply them fairly quickly, in
> > general.
> Yes, but I have the impression that patches tends to accumulate in a
> stack fashion, so the patches served are the last arrived. If a patch
> slips out of scope, it takes some time to get reviewed/committed. This
> is wouldn't be a critic to your great work nor the work of the other
> great reviewer/committers!

Yes, I agree this is what happens, but there is more or less a reason
for it. When a new patch arrives, if it's a fairly trivial package
bump, hash addition, or new package addition not raising any particular
question, then it's just good to apply it quickly so that it gets out
of the way.

Then, what happens is that what remains from this quick effort are the
more complicated patches, that tend to pile up.

Whenever I spend an evening applying patches, I generally try to work
in two passes: first a quick pass on all the trivial stuff of the day
(or past few days), and then a second pass during which I try to handle
a few older patches.

Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering

More information about the buildroot mailing list