* Jeff Garzik <jeff@garzik.org> wrote:

quoted text
> Ingo Molnar wrote:
>> so please tell me Jeff. If Greg, who is the super-maintainer of your 
>> code area, and who deals with your code every day and changes it 
>> every minute and hour, simply did not Cc: the SCSI list - how am i, a 
>> largely outside party in this matter, supposed to notice that 3 
>> maintainers and 3 mailing lists in the Cc: were somehow not enough 
>> and that i was supposed to grow the already sizable Cc: list even 
>> more?
>
> Because, regardless of the situation, it's both common courtesy and 
> wise practice to CC relevant driver maintainers, when you touch a 
> driver.
>
> And it's just common sense: Greg simply does not know the intimate 
> details of every PCI driver.  Nor do I.  Nor you.
>
> In the case of lpfc here, we have an active driver maintainer, and an 
> up-to-date MAINTAINERS entry.  Even if you are too slack to read 
> MAINTAINERS, 'git log' would have given you the same info.
>
> Don't pretend there is some benefit here to ignoring the people that 
> best know the driver.  I don't buy that; it simply makes no 
> engineering sense whatsoever.

what you _STILL_ do not realize is the following: you still attribute 
the lack of Cc:s to some intention of mine. No, it was not my intention. 
At first glance the Cc: looked large and complete enough in an 
_existing_ discussion and that's was the end of my (brief) attention 
regarding the Cc: line. Yes, it would have been a bit better had i 
noticed the lack of Cc:s in an existing discussion, but i didnt.

[ And it might not surprise you if i observe here that i think this
  little mishap is further (incidental) proof that having this many
  mailing list aliases to get the 'guaranteed attention' of maintainers 
  is just super fragile and does not serve users at all. Even Greg and i 
  got it wrong accidentally. If _we_ get it wrong, who will get it 
  right? I see several mis-Cc:ed emails every day and there's over a 
  1000 unfixed bugs in bugzilla for 2.6 alone. It does not take a genius 
  to observe that something is fundamentally wrong ;-) That 2.6 works on
  your or my box is a _very_ poor metric - we both fix bugs on our 
  systems super fast so we've got a very biased first-hand experience 
  about the stability and reliability of the kernel. We never really 
  feel the kind of frustration that testers feel when their mail to lkml 
  gets ignored. We never really feel the helplessness that comes from 
  unfixed bugs. ]

	Ingo
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/