summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2014-03-15 18:44:32 +0100
committerwm4 <wm4@nowhere>2014-03-30 17:50:02 +0200
commit1e2d28f56707886d1a40470502f18c079444aeb9 (patch)
tree21cc715f88733ea74394bd940157d6e3fddb1bf6
parent89973ebca1451fc1c758124611357fb79c73eab8 (diff)
downloadmpv-1e2d28f56707886d1a40470502f18c079444aeb9.tar.bz2
mpv-1e2d28f56707886d1a40470502f18c079444aeb9.tar.xz
DOCS/coding-style: add another requirement for commit messages
-rw-r--r--DOCS/coding-style.md3
1 files changed, 3 insertions, 0 deletions
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