..David Miller wrote:
Absolutely, though to a varying degree. That's the responsibility
that goes with the role of a subsystem maintainer. I once had
such a role, and gave it up when I felt I could no longer keep up.
You still keep refering to it as "your (my) bug".
It's not. I had nothing to do with it, other than stumbling over it.
When people stumble over a libata bug, I look hard to see if my code
could possibly cause it. Jeff looks even harder, because he's the
current subsystem dude for libata.
I never suggest a user search through a mountain of unrelated commits
for something I've screwed up on. I give more directed help, patches
to collect more relevant information, and patches to try and resolve it.
The last thing I'd ever do, is diss the reporter.
Regards.
--
| James Bruce | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Peter Zijlstra | [PATCH 00/23] per device dirty throttling -v8 |
| Jan Engelhardt | intel iommu (Re: -mm merge plans for 2.6.23) |
| Peter Zijlstra | [RFC/PATCH 0/4] CPUSET driven CPU isolation |
git: | |
| Gerrit Renker | [PATCH 18/37] dccp: Support for Mandatory options |
| Rick Jones | Re: Network latency regressions from 2.6.22 to 2.6.29 |
| David Miller | [GIT]: Networking |
| Josip Rodin | bnx2_poll panicking kernel |
