Documentation: Add "how to write a good patch summary" to SubmittingPatches
authorTheodore Ts'o <tytso@mit.edu>
Thu, 16 Apr 2009 11:44:45 +0000 (07:44 -0400)
committerJonathan Corbet <corbet@lwn.net>
Thu, 4 Jun 2009 16:34:33 +0000 (10:34 -0600)
commit2ae19acaa50a09c1099956efb895c0aca74ab050
tree400180708dac8e250d9d2ad9dd2080d40b115d18
parent5801da1b2f1207da21271ffd6768cd40a6c7f1c4
Documentation: Add "how to write a good patch summary" to SubmittingPatches

Unfortunately many patch submissions are arriving with painfully poor
patch descriptions.   As a result of the discussion on LKML:

      http://lkml.org/lkml/2009/4/15/296

explain how to submit a better patch description, in the (perhaps
vain) hope that maintainers won't end up having to rewrite the git
commit logs as often as they do today.

Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
Cc: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Documentation/SubmittingPatches