git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git blame gives an ambiguous short revision

From
JLJulia Lawall <julia.lawall@lip6.fr>
Date
Jul 1, 2012, 12:31 UTC
Message-ID
<alpine.DEB.2.02.1207010830371.1873@hadrien>
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:
Show 26 quoted lines
> 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
>
Previous: Julia LawallNext: Junio C Hamano
Message 2 of 5 in “git blame gives an ambiguous short revision”
  1. Julia LawallJul 1, 2012
  2. Julia LawallJul 1, 2012
  3. Junio C HamanoJul 2, 2012
  4. Junio C HamanoJul 2, 2012
  5. Junio C HamanoJul 2, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.