The discussion was useful. I choose to agree with the people who
suggested a URL rather than with Alan's suggestion of an expanded
message. It allows vendors who want to support their customers
directly to add a reference to their policy and remove the load from
l-k.
That is what discussion is for, to bring out possibilities. If you
don't like my decision you are free to ship and maintain your own
modified version of modutils.
>I get sick and tired of maintainers who solicit opinions and then refuse
>to listen to the answers they get back, even when people who know what
>they are doing agree... even when the majority agrees. I've seen it
>happen many times. I know it's the maintainer's choice in the end, but
>don't ask for community opinions unless you're going to listen to them.
>It's insulting and infuriating.
Translation: "I don't like the decision so I will complain about the
maintainer". See above.
>I provide a module, not a distribution. I've found that people want to
>choose their distribution, even sometimes in embedded space, so I let
>them (and I have no interest in providing a distribution anyway). I
>cannot control what modutils they run. But I get bug reports back on
>the module due to the tainted message.
That is one of the many costs you have to bear for shipping binary only
modules. I am not going to make life easier for you. In your original
message to me you made no mention of the fact that you are shipping
binary only modules, if I had know that in advance I would not have
tried to help you, now you have no credibility with me.
>At the very least, -please- change the verb tense of the message to be
>correct. That will at least eliminate the "module doesn't load" bug
>reports (I hope).
The verb tense is correct. The message is issued before the module is
loaded and descibes what is about to occur.
-
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/