git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Dan Loewenherz <dloewenherz@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Bizarre behavior on git commit
Date: Wed, 5 May 2010 23:57:26 -0500	[thread overview]
Message-ID: <20100506045726.GA27055@progeny.tock> (raw)
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

  reply	other threads:[~2010-05-06  4:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05  5:46 Bizarre behavior on git commit Dan Loewenherz
2010-05-05  6:01 ` Jonathan Nieder
2010-05-05 10:06   ` Matthieu Moy
2010-05-06  3:32   ` Dan Loewenherz
2010-05-06  4:57     ` Jonathan Nieder [this message]
2010-05-05 16:52 ` Chris Packham

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100506045726.GA27055@progeny.tock \
    --to=jrnieder@gmail.com \
    --cc=dloewenherz@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).