From: Neal Gompa (ニール・ゴンパ) Date: Tue, 8 Jan 2019 17:23:05 +0000 (-0500) Subject: Bump commit subject length to 72 characters X-Git-Tag: zfs-0.7.13~12 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=b0d579bc55a8536fe6313a7627d52206322d39b9;p=zfs Bump commit subject length to 72 characters There's not really a reason to keep the subject length so short, since the reason to make it this short was for making nice renders of a summary list of the git log. With 72 characters, this still works out fine, so let's just raise it to that so that it's easier to give slightly more descriptive change summaries. Reviewed by: Matt Ahrens Reviewed-by: Tony Hutter Reviewed-by: Brian Behlendorf Signed-off-by: Neal Gompa Closes #8250 --- diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md index c2a5e6a13..08871f752 100644 --- a/.github/CONTRIBUTING.md +++ b/.github/CONTRIBUTING.md @@ -161,7 +161,7 @@ coding convention. ### Commit Message Formats #### New Changes Commit messages for new changes must meet the following guidelines: -* In 50 characters or less, provide a summary of the change as the +* In 72 characters or less, provide a summary of the change as the first line in the commit message. * A body which provides a description of the change. If necessary, please summarize important information such as why the proposed diff --git a/scripts/commitcheck.sh b/scripts/commitcheck.sh index e9454b036..b749e238d 100755 --- a/scripts/commitcheck.sh +++ b/scripts/commitcheck.sh @@ -50,10 +50,10 @@ function new_change_commit() { error=0 - # subject is not longer than 50 characters - long_subject=$(git log -n 1 --pretty=%s "$REF" | grep -E -m 1 '.{51}') + # subject is not longer than 72 characters + long_subject=$(git log -n 1 --pretty=%s "$REF" | grep -E -m 1 '.{73}') if [ -n "$long_subject" ]; then - echo "error: commit subject over 50 characters" + echo "error: commit subject over 72 characters" error=1 fi