From: nathan.panike@gmail.com
To: git@vger.kernel.org
Subject: [BUG] in rev-parse
Date: Wed, 14 Dec 2011 12:49:27 -0600 [thread overview]
Message-ID: <20111214184926.GB18335@llunet.cs.wisc.edu> (raw)
In my local git.git:
$ git rev-parse 73c6b3575bc638b7096ec913bd91193707e2265d^@
57526fde5df201a99afa6d122c3266b3a1c5673a
942e6baa92846e5628752c65a22bc4957d8de4d0
$ git rev-parse --short 73c6b3575bc638b7096ec913bd91193707e2265d^@
57526fd
942e6ba
fatal: Needed a single revision
^^^ I don't believe this "fatal" message should be here
$ git version
git version 1.7.8
Nathan Panike
next reply other threads:[~2011-12-14 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 18:49 nathan.panike [this message]
2011-12-14 21:01 ` [BUG] in rev-parse Jeff King
2011-12-15 3:20 ` Junio C Hamano
2011-12-15 7:05 ` Jeff King
2011-12-15 17:43 ` Junio C Hamano
2011-12-15 22:53 ` Michael Haggerty
2011-12-17 12:02 ` Jeff King
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=20111214184926.GB18335@llunet.cs.wisc.edu \
--to=nathan.panike@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).