From: kristofferhaugsbakk@fastmail.com
To: git@vger.kernel.org, jonatan@jontes.page
Cc: Kristoffer Haugsbakk <code@khaugsbakk.name>,
benknoble@gmail.com, gitster@pobox.com, peff@peff.net,
sandals@crustytoothpaste.net
Subject: [PATCH v7 5/4] doc: config: fix list continuation in alias section
Date: Mon, 23 Feb 2026 18:09:00 +0100 [thread overview]
Message-ID: <followup-alias-i18n.3e0@msgid.xyz> (raw)
From: Kristoffer Haugsbakk <code@khaugsbakk.name>
ac1f12a9 (alias: support non-alphanumeric names via subsection syntax,
2026-02-18) did not use list continuation for this code block[1] which
means that the block ends after it. In turn the paragraph starting with
`git last` goes to the outer block and the next paragraphs are not
continued properly.
We can simply add list continuation right before and after the code
block. Let’s of course do that, but let’s also change to use a non-
indented code block (----) in line with the preceding configuration
example.
Also use `$ #` for the comment to be consistent with
the terminal prompt.
† 1: From https://lore.kernel.org/git/xmqqqzqqrk2h.fsf@gitster.g/
Signed-off-by: Kristoffer Haugsbakk <code@khaugsbakk.name>
---
Notes (series):
Notes to the maintainer:
This is based on top of jh/alias-i18n (merged to
`next` on 2026-02-20 at b9a5c15c4f).
See: https://lore.kernel.org/git/112cccfd-ee04-4c23-bc5e-fd269ebc6c1f@app.fastmail.com/#t
Documentation/config/alias.adoc | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
diff --git a/Documentation/config/alias.adoc b/Documentation/config/alias.adoc
index 115fdbb1e3f..dc04b0b4bfe 100644
--- a/Documentation/config/alias.adoc
+++ b/Documentation/config/alias.adoc
@@ -30,11 +30,13 @@ Examples:
----
+
With a Git alias defined, e.g.,
-
- $ git config --global alias.last "cat-file commit HEAD"
- # Which is equivalent to
- $ git config --global alias.last.command "cat-file commit HEAD"
-
++
+----
+$ git config --global alias.last "cat-file commit HEAD"
+$ # Which is equivalent to
+$ git config --global alias.last.command "cat-file commit HEAD"
+----
++
`git last` is equivalent to `git cat-file commit HEAD`. To avoid
confusion and troubles with script usage, aliases that
hide existing Git commands are ignored except for deprecated
base-commit: edd8ad18a643d47dd92b08ab865bf7f4a26f50bc
--
2.53.0.26.g2afa8602a26
reply other threads:[~2026-02-23 17:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=followup-alias-i18n.3e0@msgid.xyz \
--to=kristofferhaugsbakk@fastmail.com \
--cc=benknoble@gmail.com \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jonatan@jontes.page \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox