From: "Kristoffer Haugsbakk" <code@khaugsbakk•name>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>,
git@vger•kernel.org, "Jean-Noël AVILA" <jn.avila@free•fr>
Subject: Re: [PATCH 1/4] doc: am: normalize git(1) command links
Date: Wed, 11 Feb 2026 18:32:15 +0100 [thread overview]
Message-ID: <1a05ca33-dda0-4315-970d-b61a3f48a8f4@app.fastmail.com> (raw)
In-Reply-To: <git-am_gitlinks.322@msgid.xyz>
On Mon, Feb 9, 2026, at 18:34, kristofferhaugsbakk@fastmail•com wrote:
> From: Kristoffer Haugsbakk <code@khaugsbakk•name>
>
> There are many mentions of commands using inline-verbatim or
> emphasis ('). We just mention the command themselves, not specific
> invocations like `git am <opts>`. Let’s link to them instead.
>
> There are also many such mentions which then link to the command right
> afterwards. Simplify to just using a link.
>
> Also remove “see <gitlink>” phrases where they have now already
> been mentioned.
>
> Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk•name>
>[snip]
> diff --git a/Documentation/git-am.adoc b/Documentation/git-am.adoc
>[snip]
> Valid <action> for the `--whitespace` option are:
> `nowarn`, `warn`, `fix`, `error`, and `error-all`.
> @@ -205,7 +203,8 @@ applying.
> to the screen before exiting. This overrides the
> standard message informing you to use `--continue`
> or `--skip` to handle the failure. This is solely
> - for internal use between 'git rebase' and 'git am'.
> + for internal use between linkgit:git-rebase[1] and
> + linkgit:git-am[1].
Jean-Noël, regarding [this]. This change adds a lot of self-references:
git-am(1) inside the git-am(1) doc. Is that problematic?
[this]: https://lore.kernel.org/git/1a4060f1-6607-4b50-859d-927642eb34df@free.fr/
>[snip]
next prev parent reply other threads:[~2026-02-11 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-09 17:34 [PATCH 0/4] doc: am: improve command linking and add am.messageId kristofferhaugsbakk
2026-02-09 17:34 ` [PATCH 1/4] doc: am: normalize git(1) command links kristofferhaugsbakk
2026-02-11 17:32 ` Kristoffer Haugsbakk [this message]
2026-02-09 17:34 ` [PATCH 2/4] doc: am: say that --message-id adds a trailer kristofferhaugsbakk
2026-02-09 17:34 ` [PATCH 3/4] doc: am: add missing config am.messageId kristofferhaugsbakk
2026-02-09 17:34 ` [PATCH 4/4] doc: am: fill out hook discussion kristofferhaugsbakk
2026-02-09 21:57 ` [PATCH 0/4] doc: am: improve command linking and add am.messageId D. Ben Knoble
2026-02-09 22:22 ` 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=1a05ca33-dda0-4315-970d-b61a3f48a8f4@app.fastmail.com \
--to=code@khaugsbakk$(echo .)name \
--cc=git@vger$(echo .)kernel.org \
--cc=jn.avila@free$(echo .)fr \
--cc=kristofferhaugsbakk@fastmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox