aboutsummaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorJonathan Nieder <jrnieder@gmail.com>2010-08-20 05:38:14 -0500
committerJunio C Hamano <gitster@pobox.com>2010-08-20 14:16:50 -0700
commit3c56c84eb8d6e74a6a0457ddc3853f2f0200acb5 (patch)
treea2d9e2308debfccf8036686e33e79dfa1aa073b8 /Documentation
parent70676e69a58025ff6e224bd6f0ed80ae1b158388 (diff)
downloadgit-3c56c84eb8d6e74a6a0457ddc3853f2f0200acb5.tar.gz
git-3c56c84eb8d6e74a6a0457ddc3853f2f0200acb5.tar.xz
Documentation: avoid stray backslash in user manual
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/user-manual.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 22aee34d4..fecc4eb5b 100644
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -4251,9 +4251,9 @@ Two things are interesting here:
negative numbers in case of different errors--and 0 on success.
- the variable `sha1` in the function signature of `get_sha1()` is `unsigned
- char \*`, but is actually expected to be a pointer to `unsigned
+ char {asterisk}`, but is actually expected to be a pointer to `unsigned
char[20]`. This variable will contain the 160-bit SHA-1 of the given
- commit. Note that whenever a SHA-1 is passed as `unsigned char \*`, it
+ commit. Note that whenever a SHA-1 is passed as `unsigned char {asterisk}`, it
is the binary representation, as opposed to the ASCII representation in
hex characters, which is passed as `char *`.