summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorwm4 <wm4@nowhere>2017-06-13 22:42:12 +0200
committerwm4 <wm4@nowhere>2017-06-13 22:42:12 +0200
commitd0f807e5f38713470d307e17484e7a2441b51bb6 (patch)
tree8a93bf9bd5c4864d196f746f29f7876c8e9f30dc
parent4e37980c567da3b712ec5bc3ef9389c8c3649561 (diff)
downloadmpv-d0f807e5f38713470d307e17484e7a2441b51bb6.tar.bz2
mpv-d0f807e5f38713470d307e17484e7a2441b51bb6.tar.xz
DOCS/contribute.md: commit message body should be line-broken too
Not all tools apply line breaking. Which is probably good, because you wouldn't be able to put lines in there which should _not_ be broken. Don't ask me whether there is an "official" git convention for this.
-rw-r--r--DOCS/contribute.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/DOCS/contribute.md b/DOCS/contribute.md
index 994e2040c1..c7226ec819 100644
--- a/DOCS/contribute.md
+++ b/DOCS/contribute.md
@@ -24,8 +24,9 @@ Sending patches
the change.
- The subject line (the first line in a commit message) should contain a
prefix identifying the sub system, followed by a short description what
- impact this commit has. This subject line shouldn't be longer than 72
- characters, because it messes up the output of many git tools otherwise.
+ impact this commit has. This subject line and the commit message body
+ shouldn't be longer than 72 characters per line, because it messes up the
+ output of many git tools otherwise.
For example, you fixed a crash in af_volume.c: