Re: [BUG] git commit --allow-empty-message -m '' fails

From: Josh Hagins <hagins.josh@gmail.com>
Date: May 2, 2015, 02:44 UTC
Message-ID: <CANuW5x3oHmjAk=Ju6j+sxYnVp8mSs_V6t7YHm2S9=+0GgHnkDg@mail.gmail.com>
In-Reply-To: <20150502022924.GA587@peff.net>

Turns out it was actually scm_breeze. It defines a git() bash function and takes care of expanding arguments itself:

  https://github.com/ndbroadbent/scm_breeze/blob/master/lib/git/aliases.sh#L26

I'll open an issue there.

On Fri, May 1, 2015 at 10:29 PM, Jeff King <peff@peff.net> wrote:

Show 14 quoted lines

> On Sat, May 02, 2015 at 01:25:45AM +0000, Josh Hagins wrote:
>
>> I have git aliased to hub, which must do some preprocessing before handing
>> the command off to git.
>>
>> That's likely the culprit, but I'm using iTerm as my terminal emulator,
>> which might be doing something tricky, but I doubt it. I'll open an issue
>> on hub's GitHub repo and see what I can find out.
>
> Ah, yeah, it's probably hub. Looks like it's fixed already there:
>
>   https://github.com/github/hub/pull/727
>
> -Peff

-- 
Josh Hagins
College of Engineering
Cornell University '14
(843) 847-6008