How many fixed the problem and never published the fix?
I suspect these imagined fixers-but-never-submitters were submitters at some point in the past who never got so much as a thanky thanky back, and decided it was not worth it.
Why don't people just put a patch on a website and supply a link? Then people can take it or leave it. I don't see how it could be made any easier.
Because developers will "leave it". They don't go hunting for patches; patches have to be submitted, usually via a system like Bugzilla. It will never make it upstream (into packaged versions) and thus will languish and be forgotten.
A patch just out-there will be of little value. It very possibly won't apply to future versions or will become a bug if people do apply it. Bug/patch trackers and code repositories exist for very good reason And it would be no more hassle, bar creating the account and contact from others requesting changes, a version for new releases, etc, except
Adam Tauno Williams wrote: that the bug would be closed due to code quality (or would it? that seems to be what the poster above was suggesting). But the situation seems better in that someone trying to fix the problem would have the code for reference if they searched closed bugs (I must admit that wouldn't have occurred to me). I guess the main thing is for the developer to be specific about which kernel version it was made against. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org