From: Omri Sarig Date: Tue, 03 Mar 2026 17:07:20 GMT Subject: Re: [PATCH] doc: add information regarding external commands Message-ID: In-Reply-To: Thank you for the reply and review - a fixed patch V2 is incoming shortly. On Mon, Mar 2, 2026 at 11:56 PM Junio C Hamano wrote: > > "Omri Sarig via GitGitGadget" writes: > > > From: Omri Sarig > > > > Git supports running external commands in the user's PATH as if they > > were built-in commands (see execv_dashed_external in git.c). > > Correct. > > > This feature was not documented in any of Git's user-facing > > documentation. > > "Not documented in any" is a slight exaggeration. See "git help > git" and look at description of "--list-cmds" option; "all commands > in $PATH that have git- prefix" is mentioned there. Also "git help > help" talks about "--no-external-commands" that excludes "git-*" > commands found on $PATH from the listing, which implies these things > count as available commands. > > Nevertheless, it is a good idea to make it more discoverable. > > > This commit adds a short documentation of this feature, making it easier > > for users to discover and use. > > I would have expected that under Environment Variables > System, > next to HOME, we would add an entry for PATH that says something > like: > > When a user runs 'git ' that is not part of the core > Git programs (installed in GIT_EXEC_PATH), 'git-' that > is runnable by the user in a directory on `$PATH` is invoked. > > > or something like that; I didn't expect us to add a dedicated > separate section for it. I've added this now as you suggest. I made it slightly more verbose (adding information about the arguments for the commands, and about it taking precedence over aliases). If you want it to be shorter again, let me know and I'll remove this information. > > Thanks. > With Kind Regards, Omri