Vetter: Linux Kernel Maintainer Statistics
Vetter: Linux Kernel Maintainer Statistics
Posted Apr 27, 2018 21:24 UTC (Fri) by bfields (subscriber, #19510)In reply to: Vetter: Linux Kernel Maintainer Statistics by pbonzini
Parent article: Vetter: Linux Kernel Maintainer Statistics
I pretty much assume that pulls are exactly for the case where you're delegating review to someone else.
If I'm willing to review individual patches, I may as well apply them while I'm at it.
As I see it the advantages of a pull/merge over applying a patch series is a) it's a quicker more convenient way to merge a whole bunch of development, and b) it records *exactly* the state of the other developer's tree, so that if a problem is introduced we'll know whether it came from my tree, their tree, or the merge itself.
Both of those are most useful if I'm delegating the review to someone else rather than doing it myself.
So I'd take "X pulled Z from Y" to be a pretty strong hint that X did *not* review Y. (But rather than X trusts Y to do a good job of Z.)
