revisions.txt: be explicit about commands writing 'ORIG_HEAD'
When mentioning 'ORIG_HEAD', be explicit about which command write that pseudo-ref, namely 'git am', 'git merge', 'git rebase' and 'git reset'. Signed-off-by: Philippe Blain <levraiphilippeblain@gmail.com> Acked-by: Phillip Wood <phillip.wood@dunelm.org.uk> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Philippe Blain committed
Jan 10, 2023 at 13:15 UTC
c6eec9cb3677fe91c887181c0a184cb30627fca2
1 file changed
+2
-1
Documentation/revisions.txt
+2
-1
@@ -49,7 +49,8 @@ characters and to avoid word splitting.
49
`FETCH_HEAD` records the branch which you fetched from a remote repository
50
with your last `git fetch` invocation.
51
`ORIG_HEAD` is created by commands that move your `HEAD` in a drastic
52
-way, to record the position of the `HEAD` before their operation, so that
52
+way (`git am`, `git merge`, `git rebase`, `git reset`),
53
+to record the position of the `HEAD` before their operation, so that
54
you can easily change the tip of the branch back to the state before you ran
55
them.
56
`MERGE_HEAD` records the commit(s) which you are merging into your branch