Pulled, thanks Robert!
The way to do it is to not keep that many pending patches in the first place.
There are always 'pending patches' - if we waited for them to drain then we
could never do cleanups.
Peter, Arnaldo, Frederic and all the other perf developers sync their patches
with perf/core very frequently and push these bits to me. This has various
advantages:
- breakages are discovered quickly and can be mitigated before more harm is
done.
- patch review is a lot more gradual (and a lot less taxing) as well.
- other people can get interested and jump in and help you out.
- design mistakes/disagreements can also be hashed out before too much work
is invested into a particular direction.
- as a maintainer i can see progress and can see problem areas. This makes it
much easier to judge and plan a new topic's upstream integration schedule.
It's not tucked away in some tree, with a large stream of patches showing
up at once.
i.e. it's all variations of the 'release early, release often' Linux mantra.
So if you have a significant amount of pending patches then you are doing
something wrong. Please consider adapting your workflow and please get any
pending pieces to us in small, reviewable pieces.
That's especially true of large, intrusive features: for example the IBS bits
could be moved into perf/core gradually, in a series of clean steps, even if
they are not functional yet.
Thanks,
Ingo
--
