Dear Wolfgang Denk,
Dear =?utf-8?Q?Beno=C3=AEt_Th=C3=A9baudeau?=,
you wrote:
If it's ack'ed, why does nobody apply it? What is the normal life cycle of patches like these that don't have a custodian?
And I explained to you:
They end on my table, and probably get merged when the next merge window opens. See http://www.denx.de/wiki/U-Boot/ReleaseCycle
But you continue to ask again and again and again:
Can you apply it now that the merge window is open?
...
Can someone answer, please?
Do you have any idea why nobody applies this series and answers? Who is the fs custodian? Wolfgang since I can't find a custodian defined for fs, no? Is it because of vacations or something? I'd like if this series could be applied before the end of the current merge window.
Didn't I tell you that these will be handled by me? The when depends on when I find time to do this. I have a lot of patches on my stack, and usually I process these sequentially, and not in the order of the "priority" as the submitter wants to assign. It is perfectly OK to send a reminder when there is nothing happening, or when the merge window closes and I call for unprecessed patches to be flagged, but frankly, you ask a bit too often. You may want to read http://www.catb.org/~esr/faqs/smart-questions.html#urgent ...
Understood. Sorry for the noise. I'm still new to U-Boot mailing list, so I'm learning the rules and timings progressively. I was not asking for priority over others. It's just that you said you handled such patches when the next merge window opens, but then nothing happened when the merge window opened, even after a few weeks, so I was wondering why. Now it's clear.
Best regards, Benoît