aboutsummaryrefslogtreecommitdiff
path: root/Documentation/diff-generate-patch.txt
diff options
context:
space:
mode:
authorJunio C Hamano <gitster@pobox.com>2012-05-02 13:51:45 -0700
committerJunio C Hamano <gitster@pobox.com>2012-05-02 13:51:45 -0700
commitd274fc093cbdcddbf9aff5f79de4e9445f3363d7 (patch)
tree0abf168a8760bee8686a8836b4b29a366eab0118 /Documentation/diff-generate-patch.txt
parent1be65eda6a7018445ebdd9cfec4b1caab4db34ba (diff)
parent6cf378f0cbe7c7f944637892caeb9058c90a185a (diff)
downloadgit-d274fc093cbdcddbf9aff5f79de4e9445f3363d7.tar.xz
Merge branch 'jk/doc-asciidoc-inline-literal'
Our documentation was written for an ancient version of AsciiDoc, making the source not very readable. By Jeff King * jk/doc-asciidoc-inline-literal: docs: stop using asciidoc no-inline-literal
Diffstat (limited to 'Documentation/diff-generate-patch.txt')
-rw-r--r--Documentation/diff-generate-patch.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/diff-generate-patch.txt b/Documentation/diff-generate-patch.txt
index c57460c03d..55f499a160 100644
--- a/Documentation/diff-generate-patch.txt
+++ b/Documentation/diff-generate-patch.txt
@@ -175,7 +175,7 @@ In the above example output, the function signature was changed
from both files (hence two `-` removals from both file1 and
file2, plus `++` to mean one line that was added does not appear
in either file1 nor file2). Also eight other lines are the same
-from file1 but do not appear in file2 (hence prefixed with `{plus}`).
+from file1 but do not appear in file2 (hence prefixed with `+`).
When shown by `git diff-tree -c`, it compares the parents of a
merge commit with the merge result (i.e. file1..fileN are the