From: Dan Loewenherz <dloewenherz@gmail.com>
To: git@vger.kernel.org
Subject: Bizarre behavior on git commit
Date: Tue, 4 May 2010 22:46:07 -0700 [thread overview]
Message-ID: <s2t6f5a4e781005042246sb9ef3d48j134b22b5b41133ed@mail.gmail.com> (raw)
I'm running into a weird issue in a specific repo where "git show-ref"
usage is being displayed after invocating "git commit".
E.g.
$ git commit -m "my commit message"
usage: git show-ref [-q|--quiet] [--verify] [--head]
[-d|--dereference] [-s|--hash[=<n>]] [--abbrev[=<n>]] [--tags]
[--heads] [--] [pattern*]
or: git show-ref --exclude-existing[=pattern] < ref-list
--tags only show tags (can be combined with heads)
--heads only show heads (can be combined with tags)
--verify stricter reference checking, requires exact ref path
--head show the HEAD reference
-d, --dereference dereference tags into object IDs
-s, --hash[=<n>] only show SHA1 hash using <n> digits
--abbrev[=<n>] use <n> digits to display SHA-1s
-q, --quiet be quiet
--exclude-existing[=<pattern>]
show refs from stdin that aren't in local repository
[master 28a735f] my commit message
1 files changed, 2 insertions(+), 0 deletions(-)
$
This happens for every commit in this repository. I looked through the
git source and failed to find any reference to git show-ref (or
anything related to it) in buildin/commit.c. I gave up my search in
hope that someone on the git list would have a better idea. I'm
running version 1.7.0.3.311.g6a6955.
-Dan
next reply other threads:[~2010-05-05 5:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 5:46 Dan Loewenherz [this message]
2010-05-05 6:01 ` Bizarre behavior on git commit Jonathan Nieder
2010-05-05 10:06 ` Matthieu Moy
2010-05-06 3:32 ` Dan Loewenherz
2010-05-06 4:57 ` Jonathan Nieder
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=s2t6f5a4e781005042246sb9ef3d48j134b22b5b41133ed@mail.gmail.com \
--to=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).