On Tue, 13 November 2007 13:56:58 -0800, Andrew Morton wrote:
>
> It's relatively common that a regression in subsystem A will manifest as a
> failure in subsystem B, and the report initially lands on the desk of the
> subsystem B developers.
>
> But that's OK. The subsystem B people are the ones with the expertise to
> be able to work out where the bug resides and to help the subsystem A
> people understand what went wrong.
>
> Alas, sometimes the B people will just roll eyes and do nothing because
> they know the problem wasn't in their code. Sometimes.
And sometimes the A people will ignore the B people after the root cause
has been worked out. Do you have a good idea how to shame A into
action? Should I put you on Cc:? Right now I'm in the eye-rolling
phase.
Jörn
--
The cost of changing business rules is much more expensive for software
than for a secretaty.
-- unknown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
