summaryrefslogtreecommitdiffstats
path: root/user-manual.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2023-10-18 13:46:26 -0700
committerJunio C Hamano <gitster@pobox.com>2023-10-18 13:46:26 -0700
commit362e04f461255f3c5e6a8da6d1f4ba605438632c (patch)
tree4f2dbe0be8092ce7447e027fb74c30afd749fa03 /user-manual.txt
parentc05b7640bc119b3f3a12aec0a205031f9907613b (diff)
downloadgit-htmldocs-362e04f461255f3c5e6a8da6d1f4ba605438632c.tar.gz
Autogenerated HTML docs for v2.42.0-411-g813d9
Diffstat (limited to 'user-manual.txt')
-rw-r--r--user-manual.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/user-manual.txt b/user-manual.txt
index 428139609..d8dbe6b56 100644
--- a/user-manual.txt
+++ b/user-manual.txt
@@ -1122,7 +1122,7 @@ choosing "Stage Hunk For Commit").
=== Creating good commit messages
Though not required, it's a good idea to begin the commit message
-with a single short (less than 50 character) line summarizing the
+with a single short (no more than 50 characters) line summarizing the
change, followed by a blank line and then a more thorough
description. The text up to the first blank line in a commit
message is treated as the commit title, and that title is used