HACKING: "detailed explanation" in commit messages is almost mandatory

Signed-off-by: Stefano Lattarini <stefano.lattarini@gmail.com>

diff --git a/HACKING b/HACKING
index edafe94f1c2ce78adf328be55243e9ed248709ea..c4f0ba8157067623b5daa8e9a76cb2122c1b66d8 100644 (file)
--- a/HACKING
+++ b/HACKING
@@ -148,8 +148,9 @@
       <reference to relevant bugs, if any>
 
       Here goes a more detailed explanation of why the commit is needed,
-      and a general overview of what it does, and how.  This section is
-      optional, but you are expected to provide it more often than not.
+      and a general overview of what it does, and how.  This section
+      should almost always be provided, possibly only with the expection
+      of obvious fixes or very trivial changes.
 
       And if the detailed explanation is quite long or detailed, you can
       want to break it in more paragraphs.