On Tue, 10 Jun 2008, Alexey Dobriyan wrote:That is a valid reason, I am pretty sure everyone here (including me) has been guilty of that one. Which doesn't mean we can't do better to educate ourselves on the patterns for the most common issues. The "fix for a null-dereference to anything that has a function pointer in it" is such a pattern. THAT, however, is unacceptable IMO. If one can't be bothered, or one doesn't have the time (or the skill, whatever) to access the severity of a fix, he should ask for someone to do that on the commit message. One extra short sentence at the end of the commit message [asking for that help] is DEFINATELY not too much to ask. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh --
| Eric W. Biederman | [PATCH 02/10] sysfs: Support for preventing unmounts. |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| david | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
git: | |
| Antonio Almeida | HTB accuracy for high speed |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 26/37] dccp: Integration of dynamic feature activation - part 1 (socket set... |
| David Miller | [GIT]: Networking |
