Thread (4 messages) flat view 4 messages, 1 author, 2016-06-15
DORMANTno replies

[PATCH 1/3] Fix doc cross-refs.

From: Yann Dirson <hidden>
Date: 2016-06-15 22:43:03
Subsystem: documentation, the rest · Maintainers: Jonathan Corbet, Linus Torvalds



Signed-off-by: Yann Dirson <redacted>
---

 Documentation/stg-branch.txt |    2 +-
 Documentation/stg-clone.txt  |    4 ++--
 Documentation/stg-init.txt   |    4 ++--
 3 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/stg-branch.txt b/Documentation/stg-branch.txt
index 53f333b..28a9a28 100644
--- a/Documentation/stg-branch.txt
+++ b/Documentation/stg-branch.txt
@@ -56,7 +56,7 @@ no command, one argument::
 +
 StGIT will try to detect the branch off which the new stack is forked,
 as well as the remote repository from which that parent branch is
-taken (if any), so running stgdesc:pull[] will effectively pull new
+taken (if any), so running stglink:pull[] will effectively pull new
 commits from the correct branch.  It will warn if it cannot guess the
 parent branch (eg. if you do not specify a branch name as
 <commit-id>).
diff --git a/Documentation/stg-clone.txt b/Documentation/stg-clone.txt
index 73c0d92..126b0f2 100644
--- a/Documentation/stg-clone.txt
+++ b/Documentation/stg-clone.txt
@@ -20,8 +20,8 @@ a patch stack.
 
 This operation is for example suitable to start working using the
 "tracking branch" workflow (see gitlink:stg[1]).  Other means to setup
-an StGIT stack are stgdesc:init[] and the '--create' and '--clone'
-commands of stgdesc:branch[].
+an StGIT stack are stglink:init[] and the '--create' and '--clone'
+commands of stglink:branch[].
 
 The target directory named by <dir> will be created by this command,
 and must not exist beforehand.
diff --git a/Documentation/stg-init.txt b/Documentation/stg-init.txt
index 33fd387..e692a04 100644
--- a/Documentation/stg-init.txt
+++ b/Documentation/stg-init.txt
@@ -20,8 +20,8 @@ valid file in refs/heads/.
 
 This operation is for example suitable to start working using the
 "development branch" workflow (see gitlink:stg[1]).  Other means to setup
-an StGIT stack are stgdesc:clone[] and the '--create' and '--clone'
-commands of stgdesc:branch[].
+an StGIT stack are stglink:clone[] and the '--create' and '--clone'
+commands of stglink:branch[].
 
 OPTIONS
 -------
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help