mirrors/git
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: migrate git-commit manpage secondary files to new format

Browse Source 
Signed-off-by: Jean-Noël Avila <jn.avila@free.fr>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Jean-Noël Avila
2025-01-15 20:23:48 +00:00
committed by Junio C Hamano
parent 819fdd6e76
commit 2a13745101
2 changed files with 6 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
Documentation/i18n.txt
View File

@ -34,7 +34,7 @@ project find it more convenient to use legacy encodings, Git
does not forbid it. However, there are a few things to keep in does not forbid it. However, there are a few things to keep in
mind. mind.
. 'git commit' and 'git commit-tree' issue . `git commit` and `git commit-tree` issue
a warning if the commit log message given to it does not look a warning if the commit log message given to it does not look
like a valid UTF-8 string, unless you explicitly say your like a valid UTF-8 string, unless you explicitly say your
project uses a legacy encoding. The way to say this is to project uses a legacy encoding. The way to say this is to
@ -50,7 +50,7 @@ of `i18n.commitEncoding` in their `encoding` header. This is to
help other people who look at them later. Lack of this header help other people who look at them later. Lack of this header
implies that the commit log message is encoded in UTF-8. implies that the commit log message is encoded in UTF-8.
. 'git log', 'git show', 'git blame' and friends look at the . `git log`, `git show`, `git blame` and friends look at the
`encoding` header of a commit object, and try to re-code the `encoding` header of a commit object, and try to re-code the
log message into UTF-8 unless otherwise specified. You can log message into UTF-8 unless otherwise specified. You can
specify the desired output encoding with specify the desired output encoding with

8
Documentation/signoff-option.txt
View File

@ -1,8 +1,8 @@
ifdef::git-commit[] ifdef::git-commit[]
-s:: `-s`::
endif::git-commit[] endif::git-commit[]
--signoff:: `--signoff`::
--no-signoff:: `--no-signoff`::
Add a `Signed-off-by` trailer by the committer at the end of the commit Add a `Signed-off-by` trailer by the committer at the end of the commit
log message. The meaning of a signoff depends on the project log message. The meaning of a signoff depends on the project
to which you're committing. For example, it may certify that to which you're committing. For example, it may certify that
@ -14,5 +14,5 @@ endif::git-commit[]
leadership of the project to which you're contributing to leadership of the project to which you're contributing to
understand how the signoffs are used in that project. understand how the signoffs are used in that project.
+ +
The --no-signoff option can be used to countermand an earlier --signoff The `--no-signoff` option can be used to countermand an earlier `--signoff`
option on the command line. option on the command line.