Got it. Thanks!
On Thu, Mar 30, 2017 at 4:32 PM, Jeff King wrote:
> On Thu, Mar 30, 2017 at 04:00:41PM -0700, Nate Mueller wrote:
>
>> Really? My config has been set this way for years and it's never
>> caused problems before. I have subcommands in both of those
>> directories and all work.
>
On Thu, Mar 30, 2017 at 04:00:41PM -0700, Nate Mueller wrote:
> Really? My config has been set this way for years and it's never
> caused problems before. I have subcommands in both of those
> directories and all work.
Really. It did happen to work most of the time before (because most uses
inv
Really? My config has been set this way for years and it's never
caused problems before. I have subcommands in both of those
directories and all work.
On Thu, Mar 30, 2017 at 3:57 PM, Junio C Hamano wrote:
> Nate Mueller writes:
>
>> This fails for me because my GIT_EXEC_PATH is set to
>> "/Li
Nate Mueller writes:
> This fails for me because my GIT_EXEC_PATH is set to
> "/Library/Developer/CommandLineTools/usr/libexec/git-core:/Users/nate/.git-exec".
That environment variable is designed to hold a single path, not
like $PATH that lists multiple places in a colon separated list.
I ran into this after upgrading to 2.11.0 through Xcode. I assumed it
was a packaging issue but it looks like it's been in the mainline
since 1073094f30 (on October 29).
In 2.11.0, git-sh-setup switched it's call of git-sh-i18n from:
. git-sh-i18n
to:
. "$(git --exec-path)/git-sh-i18n"
This f
5 matches
Mail list logo
