diff options
author | Junio C Hamano <gitster@pobox.com> | 2023-12-15 12:32:44 -0800 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2023-12-15 14:08:28 -0800 |
commit | dada38646ade5041948bbe49ec21e0f2ad674109 (patch) | |
tree | c986c9c13b545acc06c66d4e4af46567c9a79c31 /Documentation/git-diff.txt | |
parent | 7122f4f7479c59da4230a1a3a129fc618cb01eee (diff) | |
download | git-dada38646ade5041948bbe49ec21e0f2ad674109.tar.gz |
docs: AUTO_MERGE is not that special
A handful of manual pages called AUTO_MERGE a "special ref", but
there is nothing special about it. It merely is yet another
pseudoref.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-diff.txt')
-rw-r--r-- | Documentation/git-diff.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-diff.txt b/Documentation/git-diff.txt index 08087ffad5..c065f023ec 100644 --- a/Documentation/git-diff.txt +++ b/Documentation/git-diff.txt @@ -103,7 +103,7 @@ Just in case you are doing something exotic, it should be noted that all of the <commit> in the above description, except in the `--merge-base` case and in the last two forms that use `..` notations, can be any <tree>. A tree of interest is the one pointed to -by the special ref `AUTO_MERGE`, which is written by the 'ort' merge +by the ref named `AUTO_MERGE`, which is written by the 'ort' merge strategy upon hitting merge conflicts (see linkgit:git-merge[1]). Comparing the working tree with `AUTO_MERGE` shows changes you've made so far to resolve textual conflicts (see the examples below). |