Junio C Hamano <junkio@xxxxxxx> wrote:
> *1* BTW, I just noticed that git-sh-setup needs to be on user's
> PATH, so we probably have to inline and duplicate the git_exec()
> shell function definition at the beginning of each script after
> all, when we make the initial ". git-sh-setup" inclusion to
> honor GIT_EXEC_PATH without munging the user's PATH.
. ${GIT_EXEC_PATH-'@@@GIT_EXEC_PATH@@@'}/git-sh-setup
isn't too grim, and shows how the git_exec shell function can be made
somewhat terser.
By the way, am I the only person who /likes/ having all the git-*
programs on his path? It makes shell completion work fairly well
without having to install strange completion scripts which get out of
date for one thing.
-- [mdw]
-
: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html