summaryrefslogtreecommitdiffstats
path: root/man1/git-commit.1
diff options
context:
space:
mode:
Diffstat (limited to 'man1/git-commit.1')
-rw-r--r--man1/git-commit.18
1 files changed, 4 insertions, 4 deletions
diff --git a/man1/git-commit.1 b/man1/git-commit.1
index 2e4c87702..5e3e27904 100644
--- a/man1/git-commit.1
+++ b/man1/git-commit.1
@@ -2,12 +2,12 @@
.\" Title: git-commit
.\" Author: [FIXME: author] [see http://www.docbook.org/tdg5/en/html/author]
.\" Generator: DocBook XSL Stylesheets vsnapshot <http://docbook.sf.net/>
-.\" Date: 2023-10-02
+.\" Date: 2023-10-04
.\" Manual: Git Manual
-.\" Source: Git 2.42.0.307.gd0e8084c65
+.\" Source: Git 2.42.0.325.g3a06386e31
.\" Language: English
.\"
-.TH "GIT\-COMMIT" "1" "2023\-10\-02" "Git 2\&.42\&.0\&.307\&.gd0e808" "Git Manual"
+.TH "GIT\-COMMIT" "1" "2023\-10\-04" "Git 2\&.42\&.0\&.325\&.g3a0638" "Git Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@@ -787,7 +787,7 @@ and
In addition to recognizing all date formats above, the \fB\-\-date\fR option will also try to make sense of other, more human\-centric date formats, such as relative dates like "yesterday" or "last Friday at noon"\&.
.SH "DISCUSSION"
.sp
-Though not required, it\(cqs a good idea to begin the commit message with a single short (less than 50 character) 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 throughout Git\&. For example, \fBgit-format-patch\fR(1) turns a commit into email, and it uses the title on the Subject line and the rest of the commit in the body\&.
+Though not required, it\(cqs a good idea to begin the commit message 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 throughout Git\&. For example, \fBgit-format-patch\fR(1) turns a commit into email, and it uses the title on the Subject line and the rest of the commit in the body\&.
.sp
Git is to some extent character encoding agnostic\&.
.sp