Skip to contentSkip to conversation

git-worktree.txt: correct linkgit command name

PATCH In review Nguyễn Thái Ngọc Duy 2 participants 2 messages Nov 3, 2018 – Nov 5, 2018 Documentation

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 git-worktree.txt: correct linkgit command name

---
On top of nd/per-worktree-ref-iteration

 Documentation/git-worktree.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/git-worktree.txt +1 -1
index 9117e4fb50..69d55f1350 100644
@@ -230,7 +230,7 @@ GIT_COMMON_DIR/worktrees/foo/HEAD and
 GIT_COMMON_DIR/worktrees/bar/refs/bisect/bad.
 
 To access refs, it's best not to look inside GIT_DIR directly. Instead
-use commands such as linkgit:git-revparse[1] or linkgit:git-update-ref[1]
+use commands such as linkgit:git-rev-parse[1] or linkgit:git-update-ref[1]
 which will handle refs correctly.
 
 DETAILS
Signature · 1 line
2.19.1.1005.gac84295441
#1 lore raw
Quoted 4 lines · Nguyễn Thái Ngọc Duy

---
On top of nd/per-worktree-ref-iteration

Thanks.

Quoted 17 lines
 Documentation/git-worktree.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
Documentation/git-worktree.txt +1 -1
index 9117e4fb50..69d55f1350 100644
@@ -230,7 +230,7 @@ GIT_COMMON_DIR/worktrees/foo/HEAD and
 GIT_COMMON_DIR/worktrees/bar/refs/bisect/bad.
 
 To access refs, it's best not to look inside GIT_DIR directly. Instead
-use commands such as linkgit:git-revparse[1] or linkgit:git-update-ref[1]
+use commands such as linkgit:git-rev-parse[1] or linkgit:git-update-ref[1]
 which will handle refs correctly.
 
 DETAILS