From: "René Scharfe" <l.s.r@web.de>
To: "Grossfeld, Michael" <Michael.Grossfeld@amd.com>,
"git@vger.kernel.org" <git@vger.kernel.org>
Cc: Jonatan Holmgren <jonatan@jontes.page>
Subject: Re: Bug: Hierarchical Aliases no longer work in 2.54.0
Date: Thu, 23 Apr 2026 23:36:39 +0200 [thread overview]
Message-ID: <ea07acab-313d-435d-8328-e601fee980c3@web.de> (raw)
In-Reply-To: <PH7PR12MB73313034573C59C73F821BBFE52A2@PH7PR12MB7331.namprd12.prod.outlook.com>
On 4/23/26 8:19 PM, Grossfeld, Michael wrote:
> Hello all! Seeing this issue on 2.54.0 and it didn't look like anyone had reported it yet.
>
>> What did you do before the bug happened? (Steps to reproduce your issue)
>
> Attempting to use the hierarchical alias "pull.sub", which was working in 2.53.0, is no longer working in 2.54.0.
> It returns the following error: "git: 'pull.sub' is not a git command. See 'git --help'."
> >> What did you expect to happen? (Expected behavior)
>
> The git alias should have firsted pulled, then updated submodules recursively.
>
>> What happened instead? (Actual behavior)
>
> It reports the following error: "git: 'pull.sub' is not a git command. See 'git --help'."
>
>> What's different between what you expected and what actually happened?
>
> git 2.53.0 to git 2.54.0.
>
>> Anything else you want to add:
>
> The alias was defined in my gitconfig as in 2.53.0, and remains this way:
>
> [alias "pull"]
> sub = "!f() { git pull origin --recurse-submodules=no --ff-only; echo Updating Submodules...; git submodule update --recursive --jobs=16 --progress; }; f"
Broken by ac1f12a9de4 (alias: support non-alphanumeric names via
subsection syntax, 2026-02-18).
Alias sections were not documented before. How did you discover them?
I think the previous behavior can be brought back while keeping the
new feature, except for aliases that end in ".command".
> It was written via this command:
> git config --global alias.pull.sub '!f() { git pull origin --recurse-submodules=no --ff-only -p; echo Updating Submodules...; git submodule update --recursive --jobs=16; }; f'
>
> Trying to do the following (with .command):
> git config --global alias.pull.sub.command '!f() { git pull origin --recurse-submodules=no --ff-only -p; echo Updating Submodules...; git submodule update --recursive --jobs=16; }; f'
>
> Results in a section of the gitconfig that looks like this:
>
> [alias "pull.sub"]
> command = "!f() { git pull origin --recurse-submodules=no --ff-only -p; echo Updating Submodules...; git submodule update --recursive --jobs=16; }; f"
Which works, right?
> [System Info]
> git version:
> git version 2.54.0.windows.1
> cpu: x86_64
> built from commit: 2b8a3ab140826ac423c2845ef81d4c6ac4f7bf3c
> sizeof-long: 4
> sizeof-size_t: 8
> shell-path: D:/git-sdk-64-build-installers/usr/bin/sh
> rust: disabled
> feature: fsmonitor--daemon
> gettext: enabled
> libcurl: 8.19.0
> OpenSSL: OpenSSL 3.5.6 7 Apr 2026
> zlib: 1.3.2
> SHA-1: SHA1_DC
> SHA-256: SHA256_BLK
> default-ref-format: files
> default-hash: sha1
> uname: Windows 10.0 26200
> compiler info: gnuc: 15.2
> libc info: no libc information available
> $SHELL (typically, interactive shell): D:\develop\tools\Git\usr\bin\bash.exe
>
> Thanks for the help!
>
> Michael Grossfeld
> AMD
next prev parent reply other threads:[~2026-04-23 22:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-23 18:19 Bug: Hierarchical Aliases no longer work in 2.54.0 Grossfeld, Michael
2026-04-23 21:12 ` Jeff King
2026-04-23 22:55 ` Michael Grossfeld
2026-04-23 21:36 ` René Scharfe [this message]
2026-04-23 22:46 ` Michael Grossfeld
2026-04-24 7:29 ` Jonatan Holmgren
2026-04-24 15:10 ` [PATCH] alias: restore support for simple dotted aliases Jonatan Holmgren
2026-04-24 16:09 ` Kristoffer Haugsbakk
2026-04-24 22:47 ` Junio C Hamano
2026-04-25 9:57 ` Jonatan Holmgren
2026-04-25 23:29 ` Jeff King
2026-04-25 23:47 ` Jeff King
2026-04-26 19:21 ` Jonatan Holmgren
2026-04-26 23:01 ` Jeff King
2026-04-27 8:36 ` Jonatan Holmgren
2026-05-12 4:43 ` Junio C Hamano
2026-05-19 0:44 ` Jeff King
2026-04-24 16:17 ` Jonatan Holmgren
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=ea07acab-313d-435d-8328-e601fee980c3@web.de \
--to=l.s.r@web.de \
--cc=Michael.Grossfeld@amd.com \
--cc=git@vger.kernel.org \
--cc=jonatan@jontes.page \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.