diff options
| author | wm4 <wm4@nowhere> | 2014-03-15 18:44:32 +0100 |
|---|---|---|
| committer | wm4 <wm4@nowhere> | 2014-03-15 18:44:32 +0100 |
| commit | e09a8ec4fa415e8df9dc1d019141b9b482ffe111 (patch) | |
| tree | 5e0821afdc0498b8c46fe5f19e8217122a01883d /DOCS | |
| parent | 5dde27601873e3bb0b20d735992669698f1a1724 (diff) | |
| download | mpv-e09a8ec4fa415e8df9dc1d019141b9b482ffe111.tar.bz2 mpv-e09a8ec4fa415e8df9dc1d019141b9b482ffe111.tar.xz | |
DOCS/coding-style: add another requirement for commit messages
Diffstat (limited to 'DOCS')
| -rw-r--r-- | DOCS/coding-style.md | 3 |
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 |