Re: Bizarre behavior on git commit

From: Jonathan Nieder <jrnieder@gmail.com>
Date: May 6, 2010, 04:57 UTC
Message-ID: <20100506045726.GA27055@progeny.tock>
In-Reply-To: <n2m6f5a4e781005052032sf47733ebwf490e0369bebd03f@mail.gmail.com>

Dan Loewenherz wrote:

>> Dan Loewenherz wrote:

>>> $ git commit -m "my commit message"
>>> usage: git show-ref [-q|--quiet] [--verify] [--head]

[...]

> The GIT_TRACE helped--it was a hook script. The script's been in my
> local repo for quite a while, strange that it only started having this
> behavior recently.

My bad.

$ git show -s v1.6.6-rc0~34^2~17
[...]
    Does anybody use "show-ref -h"?  It was in Linus's original, most
    likely only because "it might be handy", not because "the command
    should not show the HEAD by default for such and such reasons".
    So I think it is okay if "show-ref -h" (but not "show-ref
    --head") gives help and exits.
    
    If a current script uses "git show-ref -h" without any other
    arguments, it would have to be adapted by changing "-h" to
    "--head".
    
    Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
    Signed-off-by: Junio C Hamano <gitster@pobox.com>

I was too dense to notice the connection until just now.

> Removed the script and all works normally.

If you still have the script, I would be happy to look it over, for curiosity’s sake.

Cheers, Jonathan