So, you think "somebody" is willing to track all kernel issues and patches?
I don't think that's possible for any person or automated system. [it's possible with a
combination of -people- and -automation-, IMHO, though]
> > Also, obviously nobody actually took over maintainership of the patch,
> > because equally obviously nobody has been pinging me about it.
>
> I.E. patches get dropped, even when there's intense interest about them, due
> to sheer frustration burning out the patch's maintainer, and scaring away
> other potential maintainers. (Is this NOT the case? I could be wrong.
> Please point out the flaw in my logic...)
I would point out a flaw if I actually saw any logic...
Are you talking about the EA patch? See Nathan's response and other responses in this
thread.
> > For some
> > reason you seem to want _me_ to go out of my way to search for patches
> > that are over a month old that I don't know whether they are valid or not,
> > used or not, or even agreed upon or not.
>
> I thought I was actually proposing somebody else be formally tasked with the
> job of doing that...
You clearly do not realize the enormity of the task.
> > But yes, it's so much easier to blame me.
>
> Maybe just to suggest that you could use a secretary?
I suggest that you need a Valium.
Jeff
-
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/