git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Yann Dirson <ydirson@altern.org>
Date
Apr 8, 2007, 15:12 UTC
Message-ID
<20070408151205.8884.44977.stgit@gandelf.nowhere.earth>
In-Reply-To
<20070408150822.8884.67664.stgit@gandelf.nowhere.earth>
Signed-off-by: Yann Dirson <ydirson@altern.org>
---
 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
 -------
Previous: Yann DirsonNext: Yann Dirson
Message 2 of 4 in “More stgit doc updates”
  1. 0/3 More stgit doc updatesYann Dirson, Apr 8, 2007
  2. 1/3 Fix doc cross-refs.Yann Dirson, Apr 8, 2007
  3. 2/3 Make the documentation of options more consistent.Yann Dirson, Apr 8, 2007
  4. 3/3 Stop advertising 'pull' as the only operation blocked on protected stacks.Yann Dirson, Apr 8, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.