From: Junio C Hamano <gitster@pobox.com>
To: "Omri Sarig via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Omri Sarig <omri.sarig13@gmail.com>
Subject: Re: [PATCH] doc: add information regarding external commands
Date: Mon, 02 Mar 2026 14:56:18 -0800 [thread overview]
Message-ID: <xmqqqzq1x2lp.fsf@gitster.g> (raw)
In-Reply-To: <pull.2220.git.git.1772479907062.gitgitgadget@gmail.com> (Omri Sarig via GitGitGadget's message of "Mon, 02 Mar 2026 19:31:47 +0000")
"Omri Sarig via GitGitGadget" <gitgitgadget@gmail.com> writes:
> From: Omri Sarig <omri.sarig13@gmail.com>
>
> 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 <command>' that is not part of the core
Git programs (installed in GIT_EXEC_PATH), 'git-<command>' 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.
Thanks.
next prev parent reply other threads:[~2026-03-02 22:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 19:31 [PATCH] doc: add information regarding external commands Omri Sarig via GitGitGadget
2026-03-02 22:56 ` Junio C Hamano [this message]
2026-03-03 17:07 ` Omri Sarig
2026-03-03 17:12 ` [PATCH v2] " Omri Sarig via GitGitGadget
2026-03-03 17:43 ` [PATCH v3] " Omri Sarig via GitGitGadget
2026-03-03 18:40 ` Junio C Hamano
2026-03-03 18:48 ` D. Ben Knoble
2026-03-03 20:11 ` Omri Sarig
2026-03-03 20:36 ` Junio C Hamano
2026-03-04 15:03 ` [PATCH v4] " Omri Sarig via GitGitGadget
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=xmqqqzq1x2lp.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=omri.sarig13@gmail.com \
/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.