ng it wrong ;)
snip
> Another possible motivation (the one that led me to use this mechnism
> long ago) is avoiding providing the dashed form git-$cmd in $PATH. I
> think time has shown that having git-$cmd in $PATH is not too painful.
In my case, yes, I'm maintaining commands but do
For end users making use of a custom exec path many commands will simply
fail. Adding git's exec path to the PATH also allows overriding git-sh-*
scripts, not just adding commands. One can then patch a script without
tainting their system installation of git for example.
Signed-off-by:
2 matches
Mail list logo