From 1e2d28f56707886d1a40470502f18c079444aeb9 Mon Sep 17 00:00:00 2001 From: wm4 Date: Sat, 15 Mar 2014 18:44:32 +0100 Subject: DOCS/coding-style: add another requirement for commit messages --- DOCS/coding-style.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/DOCS/coding-style.md b/DOCS/coding-style.md index 8174a92436..45f838d06b 100644 --- a/DOCS/coding-style.md +++ b/DOCS/coding-style.md @@ -130,6 +130,9 @@ Sending patches tools usually do not break text automatically. On the other hand, you do not need to break text that would be unnatural to break (like data for test cases, or long URLs). + + Important: put an empty line between the subject line and the commit message. + If this is missing, it will break display in common git tools. - Try to separate cosmetic and functional changes. It's ok to make a few additional cosmetic changes in the same file you're working on, but don't do something like reformatting a whole file and hiding an actual functional -- cgit v1.2.3