All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yehezkel Bernat via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: Yehezkel Bernat <yehezkelshb@gmail.com>,
	Yehezkel Bernat <yehezkelshb@gmail.com>
Subject: [PATCH] Documentation: fix linkgit reference
Date: Sun, 14 Apr 2024 22:08:02 +0000	[thread overview]
Message-ID: <pull.1706.git.git.1713132482976.gitgitgadget@gmail.com> (raw)

From: Yehezkel Bernat <yehezkelshb@gmail.com>

In git-replay documentation, linkgit to git-rev-parse is missing the man
section which breaks its rendering

Add section number as done in other references to this command

Signed-off-by: Yehezkel Bernat <YehezkelShB@gmail.com>
---
    Documentation: fix linkgit reference

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-git-1706%2FYehezkelShB%2Fyb%2Ffix-linkgit-reference-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-git-1706/YehezkelShB/yb/fix-linkgit-reference-v1
Pull-Request: https://github.com/git/git/pull/1706

 Documentation/git-replay.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/git-replay.txt b/Documentation/git-replay.txt
index f6c269c62d5..8f3300c683a 100644
--- a/Documentation/git-replay.txt
+++ b/Documentation/git-replay.txt
@@ -46,7 +46,7 @@ the new commits (in other words, this mimics a cherry-pick operation).
 	Range of commits to replay. More than one <revision-range> can
 	be passed, but in `--advance <branch>` mode, they should have
 	a single tip, so that it's clear where <branch> should point
-	to. See "Specifying Ranges" in linkgit:git-rev-parse and the
+	to. See "Specifying Ranges" in linkgit:git-rev-parse[1] and the
 	"Commit Limiting" options below.
 
 include::rev-list-options.txt[]

base-commit: 8f7582d995682f785e80e344197cc715e6bc7d8e
-- 
gitgitgadget

             reply	other threads:[~2024-04-14 22:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-14 22:08 Yehezkel Bernat via GitGitGadget [this message]
2024-04-15  7:22 ` [PATCH] Documentation: fix linkgit reference Patrick Steinhardt
2024-04-15 18:02   ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=pull.1706.git.git.1713132482976.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=yehezkelshb@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.