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

Re: [PATCH] doc: rerere-options.adoc: link to git-rerere(1)

From
D. Ben Knoble <ben.knoble@gmail.com>
Date
Feb 9, 2026, 21:57 UTC
Message-ID
<CALnO6CAET9GOsNCdmd3_Jp5Qr3Rfxn8cgmu9n0N8s7uNYpCchg@mail.gmail.com>
In-Reply-To
<doc_link_rerere.328@msgid.xyz>
On Mon, Feb 9, 2026 at 1:14 PM <kristofferhaugsbakk@fastmail.com> wrote:
Show 27 quoted lines
>
> From: Kristoffer Haugsbakk <code@khaugsbakk.name>
>
> Five commands include these options. Let’s link to the command so that
> the curious user can learn more about what “rerere” is about.
>
> Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
> ---
>
> Notes (series):
>     Topic name: kh/doc-link-rerere
>
>  Documentation/rerere-options.adoc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/rerere-options.adoc b/Documentation/rerere-options.adoc
> index b0b920144a6..115882edab1 100644
> --- a/Documentation/rerere-options.adoc
> +++ b/Documentation/rerere-options.adoc
> @@ -4,6 +4,6 @@
>         the current conflict to update the files in the working
>         tree, allow it to also update the index with the result of
>         resolution.  `--no-rerere-autoupdate` is a good way to
> -       double-check what `rerere` did and catch potential
> +       double-check what linkgit:git-rerere[1] did and catch potential
>         mismerges, before committing the result to the index with a
>         separate `git add`.
Minor: should this adjacent be linkgit too? I thought yes, but on
second read we really are talking about the command.
Anyway, agreed that rerere should get linked. Thanks!
-- 
D. Ben Knoble
Previous: kristofferhaugsbakk@fastmail.comNext: Junio C Hamano
Message 2 of 10 in “doc: rerere-options.adoc: link to git-rerere(1)”
  1. doc: rerere-options.adoc: link to git-rerere(1)kristofferhaugsbakk@fastmail.com, Feb 9, 2026
  2. D. Ben KnobleFeb 9, 2026
  3. Junio C HamanoFeb 9, 2026
  4. Ben KnobleFeb 9, 2026
  5. Kristoffer HaugsbakkFeb 9, 2026
  6. doc: rerere-options.adoc: link to git-rerere(1)kristofferhaugsbakk@fastmail.com, Feb 10, 2026
  7. D. Ben KnobleFeb 10, 2026
  8. Jean-Noël AvilaFeb 11, 2026
  9. Junio C HamanoFeb 11, 2026
  10. Jean-Noël AvilaFeb 12, 2026

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.