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.114
1 files changed, 7 insertions, 7 deletions
diff --git a/man1/git-commit.1 b/man1/git-commit.1
index db38fbae9..0073a82b5 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-20
+.\" Date: 2023-10-23
.\" Manual: Git Manual
-.\" Source: Git 2.42.0.424.gceadf0f3cf
+.\" Source: Git 2.42.0.482.g2e8e77cbac
.\" Language: English
.\"
-.TH "GIT\-COMMIT" "1" "2023\-10\-20" "Git 2\&.42\&.0\&.424\&.gceadf0" "Git Manual"
+.TH "GIT\-COMMIT" "1" "2023\-10\-23" "Git 2\&.42\&.0\&.482\&.g2e8e77" "Git Manual"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
@@ -847,7 +847,7 @@ Although we encourage that the commit log messages are encoded in UTF\-8, both t
\fIgit commit\fR
and
\fIgit commit\-tree\fR
-issues a warning if the commit log message given to it does not look like a valid UTF\-8 string, unless you explicitly say your project uses a legacy encoding\&. The way to say this is to have
+issue a warning if the commit log message given to it does not look like a valid UTF\-8 string, unless you explicitly say your project uses a legacy encoding\&. The way to say this is to have
\fBi18n\&.commitEncoding\fR
in
\fB\&.git/config\fR
@@ -866,7 +866,7 @@ file, like this:
.sp
Commit objects created with the above setting record the value of
\fBi18n\&.commitEncoding\fR
-in its
+in their
\fBencoding\fR
header\&. This is to help other people who look at them later\&. Lack of this header implies that the commit log message is encoded in UTF\-8\&.
.RE
@@ -920,7 +920,7 @@ This setting overrides the default of the
option in
\fBgit commit\fR\&. See
\fBgit-commit\fR(1)
-for details\&. Changing the default can be useful when you always want to keep lines that begin with comment character
+for details\&. Changing the default can be useful when you always want to keep lines that begin with the comment character
\fB#\fR
in your log message, in which case you would do
\fBgit config commit\&.cleanup whitespace\fR
@@ -946,7 +946,7 @@ Specify the pathname of a file to use as the template for new commit messages\&.
.PP
commit\&.verbose
.RS 4
-A boolean or int to specify the level of verbose with
+A boolean or int to specify the level of verbosity with
\fBgit commit\fR\&. See
\fBgit-commit\fR(1)\&.
.RE