Fix passwd(5) ref and reflect that commit doens't use commit-tree
Signed-off-by: Jonas Fonseca <fonseca@diku.dk> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jonas Fonseca committed
Sep 3, 2008 at 10:50 UTC
73bae1dc468734bad3ff7d1b8e93e7ac5f9d3dff
3 files changed
+6
-6
Documentation/git-commit-tree.txt
+2
-2
@@ -79,9 +79,9 @@ Diagnostics
79
You don't exist. Go away!::
80
The passwd(5) gecos field couldn't be read
81
Your parents must have hated you!::
82
- The password(5) gecos field is longer than a giant static buffer.
82
+ The passwd(5) gecos field is longer than a giant static buffer.
83
Your sysadmin must hate you!::
84
- The password(5) name field is longer than a giant static buffer.
84
+ The passwd(5) name field is longer than a giant static buffer.
85
86
Discussion
87
----------
Documentation/git-var.txt
+3
-3
@@ -20,7 +20,7 @@ OPTIONS
20
Cause the logical variables to be listed. In addition, all the
21
variables of the git configuration file .git/config are listed
22
as well. (However, the configuration variables listing functionality
23
- is deprecated in favor of 'git-config -l'.)
23
+ is deprecated in favor of 'git config -l'.)
24
25
EXAMPLE
26
--------
@@ -41,9 +41,9 @@ Diagnostics
41
You don't exist. Go away!::
42
The passwd(5) gecos field couldn't be read
43
Your parents must have hated you!::
44
- The password(5) gecos field is longer than a giant static buffer.
44
+ The passwd(5) gecos field is longer than a giant static buffer.
45
Your sysadmin must hate you!::
46
- The password(5) name field is longer than a giant static buffer.
46
+ The passwd(5) name field is longer than a giant static buffer.
47
48
SEE ALSO
49
--------
Documentation/i18n.txt
+1
-1
@@ -21,7 +21,7 @@ project find it more convenient to use legacy encodings, git
21
does not forbid it. However, there are a few things to keep in
22
mind.
23
24
-. 'git-commit-tree' (hence, 'git-commit' which uses it) issues
24
+. 'git-commit' and 'git-commit-tree' issues
25
a warning if the commit log message given to it does not look
26
like a valid UTF-8 string, unless you explicitly say your
27
project uses a legacy encoding. The way to say this is to