doc: rerere-options.adoc: link to git-rerere(1)
Five commands include these options. Let’s link to the command so that the curious user can learn more about what “rerere” is about. It’s also better to consistently refer to things like e.g. “git-subcommand(1)” over `git subcommand` or `subcommand`. Also apply the same treatment to git-add(1). Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Kristoffer Haugsbakk committed
Feb 10, 2026 at 20:56 UTC
6bfef81c9a2ce5a64ef82fc41164fbdd4713f57a
1 file changed
+2
-2
Documentation/rerere-options.adoc
+2
-2
@@ -4,6 +4,6 @@
4
the current conflict to update the files in the working
5
tree, allow it to also update the index with the result of
6
resolution. `--no-rerere-autoupdate` is a good way to
7
- double-check what `rerere` did and catch potential
7
+ double-check what linkgit:git-rerere[1] did and catch potential
8
mismerges, before committing the result to the index with a
9
- separate `git add`.
9
+ separate linkgit:git-add[1].