From: Paul Gortmaker <paul.gortma...@windriver.com> Date: Thu, 16 Aug 2012 21:34:25 -0400
> Also, a patch should describe the problem it solves (i.e. the symptom > the end user sees), and how the problem originated, and why the fix > in the patch is the _right_ fix. The worst description a commit log > can have is one that just describes the C change in words, since > most people can read C on their own. I've frankly given up on Fan Du submitting sophisticated patches that are easy to review and are properly documented. Just getting simple things like a WORKING EMAIL ADDRESS was beyond a struggle. So when I get a patch that applies, from a properly working email address, it's an accomplishment. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
