From: Julia Lawall <julia.lawall@lip6.fr>
To: git@vger.kernel.org
Subject: Re: git blame gives an ambiguous short revision
Date: Sun, 1 Jul 2012 08:31:09 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1207010830371.1873@hadrien> (raw)
In-Reply-To: <alpine.DEB.2.02.1207010825370.1873@hadrien>
Sorry, I forgot the git version number:
git version 1.7.3.4
on Ubuntu.
julia
On Sun, 1 Jul 2012, Julia Lawall wrote:
> Using linux-next cloned today (July 1), I then checkout out the
> revision 60d5c9f5b. The command
>
> git blame drivers/staging/brcm80211/brcmfmac/wl_iw.c -L3675,3675
>
> then gives:
>
> 60d5c9f5 (Julia Lawall 2011-04-01 16:23:42 +0200 3675) if (!iscan->iscan_ex_params_p) {
>
> Then I try:
>
> git show 60d5c9f5
>
> which gives:
>
> error: short SHA1 60d5c9f5 is ambiguous.
> error: short SHA1 60d5c9f5 is ambiguous.
> fatal: ambiguous argument '60d5c9f5': unknown revision or path not in the
> working tree.
> Use '--' to separate paths from revisions
>
> If I give git blame the -l option, every thing is fine.
>
> thanks,
> julia
>
next prev parent reply other threads:[~2012-07-01 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-01 12:30 git blame gives an ambiguous short revision Julia Lawall
2012-07-01 12:31 ` Julia Lawall [this message]
2012-07-02 7:17 ` Junio C Hamano
2012-07-02 7:28 ` Junio C Hamano
2012-07-02 7:54 ` Junio C Hamano
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=alpine.DEB.2.02.1207010830371.1873@hadrien \
--to=julia.lawall@lip6.fr \
--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