Skip to contentSkip to conversation

Documentation: fix linkgit reference

PATCH In review Yehezkel Bernat via GitGitGadget 3 participants 3 messages Apr 14, 2024 – Apr 15, 2024 Documentation

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 Documentation: fix linkgit reference

From: Yehezkel Bernat <[email protected]>

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

---
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(-)
Documentation/git-replay.txt +1 -1
index f6c269c62d5..8f3300c683a 100644
@@ -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

Signature · 1 line
gitgitgadget
#1 lore raw
Quoted 6 lines · Yehezkel Bernat via GitGitGadget

From: Yehezkel Bernat <[email protected]>

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

Nit: sentences should end with a dot.

Quoted 1 line

Other than that this patch looks good to me, thanks!

Patrick

Quoted 28 lines

---
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(-)
Documentation/git-replay.txt +1 -1
index f6c269c62d5..8f3300c683a 100644
@@ -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

Signature · 1 line
gitgitgadget
#2 lore raw
Quoted 8 lines · Patrick Steinhardt
Quoted 6 lines · Yehezkel Bernat via GitGitGadget

From: Yehezkel Bernat <[email protected]>

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

Quoted 7 lines

Nit: sentences should end with a dot.

Quoted 1 line

Other than that this patch looks good to me, thanks!

Patrick

Thanks, both. Will just tweak the proposed log message while queuing.

Quoted 28 lines
Quoted 28 lines

---
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(-)
Documentation/git-replay.txt +1 -1
index f6c269c62d5..8f3300c683a 100644
@@ -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

Signature · 1 line
gitgitgadget