commit - 19a7924f3e98de860b409b8480b10b57ce16914e
commit + e764eb5bc6671e7ecb9af487ced338743d239686
blob - 149fcba8cbdc4b369202dd5851e3e3aa63ed24d4
blob + 88a4286fff9c196d6fcc50a06ce49f886eb81d91
--- got/got.1
+++ got/got.1
and
.Qq :head
can also be used to represent the work tree's base commit
-and HEAD reference, respectively.
+and branch head, respectively.
Keywords and reference names may be appended with
.Qq :+
or
Nth descendant or antecedent, respectively, by first parent traversal;
for example,
.Sy :head:-2
-denotes the HEAD reference's 2nd generation ancestor, and
+denotes the work tree branch head's 2nd generation ancestor, and
.Sy :base:+4
denotes the 4th generation descendant of the work tree's base commit.
Similarly,
and
.Qq :head
can also be used to represent the work tree's base commit
-and HEAD reference, respectively.
+and branch head, respectively.
The former is only valid if invoked in a work tree, while the latter will
resolve to the tip of the work tree's current branch if invoked in a
work tree, otherwise it will resolve to the repository's HEAD reference.
and
.Qq :head
can also be used to represent the work tree's base commit
-and HEAD reference, respectively.
+and branch head, respectively.
The former is only valid if invoked in a work tree, while the latter will
resolve to the tip of the work tree's current branch if invoked in a
work tree, otherwise it will resolve to the repository's HEAD reference.