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-merge.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-merge.txt')
| -rw-r--r-- | Documentation/git-merge.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/git-merge.txt b/Documentation/git-merge.txt index e8ab340319..3e9557a44b 100644 --- a/Documentation/git-merge.txt +++ b/Documentation/git-merge.txt @@ -196,7 +196,7 @@ happens: can inspect the stages with `git ls-files -u`). The working tree files contain the result of the merge operation; i.e. 3-way merge results with familiar conflict markers `<<<` `===` `>>>`. -5. A special ref `AUTO_MERGE` is written, pointing to a tree +5. A ref named `AUTO_MERGE` is written, pointing to a tree corresponding to the current content of the working tree (including conflict markers for textual conflicts). Note that this ref is only written when the 'ort' merge strategy is used (the default). |