On Sun, Apr 5, 2015 at 5:51 PM, Roland Dreier <roland@xxxxxxxxxx> wrote:
> On Sat, Apr 4, 2015 at 10:15 PM, Or Gerlitz <gerlitz.or@xxxxxxxxx> wrote:
>> Indeed. No maintainer voice makes it kind of impossible for
>> discussions to converge. What happens over the last years is that when
>> there's no easy consensus on matter Y, everyone stops breathing and
>> wait to see what happens on the rc1 night, b/c Roland doesn't spell
>> his view/preference (nor exposes his for-next branch till the last
>> minute, see now) many times it seems more as coin flipping.
>
> To me this attitude shows a failure of the community. If I need to
> make every decision, then that doesn't scale. People can ask
> questions a lot more easily than I can answer them.
>
> In general if a consensus emerges, I'm pretty likely to trust it. In
> particular, as Sean mentioned, I tend to trust vendors about low-level
> drivers, although of course I sometimes catch mistakes even then.
>
> But for changes that touch the core, when there's a disagreement, you
> can't expect me to be the one who always solves it. I might have an
> opinion, but in a lot of cases, both sides might have a point and the
> only way forward is to come up with a new idea that works for
> everyone. And I'm not smart enough to come up with that solution every time.
To make it a little more clear, my rc1 night note came to describe
situations where
not only that you didn't do the essential part of subsystem maintainer
job of dropping
a note on how you see things and where yo think the solution should be
going etc --
you went ahead and kind of randomly applied patch series for which there was no
consensus or bunch of open reviewer comments unanswered by the
submitters to your
for-next branch which you didn't post publicly and in < 12h sent pull
request to Linus, crazy!!
BTW as we speak now (after rc7), the patches you already have for 4.1
(and there are such, as you acked
@ least one series on the list {BTW about 5y ago you stopped for 90%
of the cases to ack pactches
on the list, which is very frustrating for developers too}) aren't
public, you have a private clone which isn't
reflected at kernel.org
Or.
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
