doc: migrate git-commit manpage secondary files to new format
Signed-off-by: Jean-Noël Avila <jn.avila@free.fr> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jean-Noël Avila committed
Jan 15, 2025 at 20:23 UTC
2a137451012657aa06d702c5b01c06c15ddae17a
2 files changed
+6
-6
Documentation/i18n.txt
+2
-2
@@ -34,7 +34,7 @@ project find it more convenient to use legacy encodings, Git
34
does not forbid it. However, there are a few things to keep in
35
mind.
36
37
-. 'git commit' and 'git commit-tree' issue
37
+. `git commit` and `git commit-tree` issue
38
a warning if the commit log message given to it does not look
39
like a valid UTF-8 string, unless you explicitly say your
40
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
50
help other people who look at them later. Lack of this header
51
implies that the commit log message is encoded in UTF-8.
52
53
-. 'git log', 'git show', 'git blame' and friends look at the
53
+. `git log`, `git show`, `git blame` and friends look at the
54
`encoding` header of a commit object, and try to re-code the
55
log message into UTF-8 unless otherwise specified. You can
56
specify the desired output encoding with
Documentation/signoff-option.txt
+4
-4
@@ -1,8 +1,8 @@
1
ifdef::git-commit[]
2
--s::
2
+`-s`::
3
endif::git-commit[]
4
---signoff::
5
---no-signoff::
4
+`--signoff`::
5
+`--no-signoff`::
6
Add a `Signed-off-by` trailer by the committer at the end of the commit
7
log message. The meaning of a signoff depends on the project
8
to which you're committing. For example, it may certify that
@@ -14,5 +14,5 @@ endif::git-commit[]
14
leadership of the project to which you're contributing to
15
understand how the signoffs are used in that project.
16
+
17
-The --no-signoff option can be used to countermand an earlier --signoff
17
+The `--no-signoff` option can be used to countermand an earlier `--signoff`
18
option on the command line.