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

':/<oneline prefix>' notation doesn't support full file syntax

From
EREric Raible <raible@gmail.com>
Date
Jul 3, 2008, 05:42 UTC
Message-ID
<279b37b20807022242q69ad2fcbwb8c11a9d6165272d@mail.gmail.com>

Although the rev-parse documentation claims that the tree-ish:path/to/file syntax works is applicable, this is not so when using the :/ "oneline prefix" syntax:

% git rev-parse v1.5.0.1-227-g28a4d94 28a4d940443806412effa246ecc7768a21553ec7 % git rev-parse ":/object name" 28a4d940443806412effa246ecc7768a21553ec7

% git rev-parse v1.5.0.1-227-g28a4d94:sha1_name.c 0781477a71ac4d76a1b8783868d6649cae7f8507 % git rev-parse ":/object name":sha1_name.c :/object name:sha1_name.c fatal: ambiguous argument ':/object name:sha1_name.c': unknown revision or path not in the working tree. Use '--' to separate paths from revisions

A quick look at int sha1_name.c:get_sha1() shows that it doesn't even try to make this work. Is this worth fixing? Or at least documenting?

- Eric
Next: Junio C Hamano
Message 1 of 9 in “':/<oneline prefix>' notation doesn't support full file syntax”
  1. Eric RaibleJul 3, 2008
  2. Junio C HamanoJul 3, 2008
  3. Eric RaibleJul 3, 2008
  4. Johannes SchindelinJul 3, 2008
  5. Dana HowJul 3, 2008
  6. Junio C HamanoJul 3, 2008
  7. Johannes SchindelinJul 4, 2008
  8. Johannes SchindelinJul 4, 2008
  9. Jeff KingJul 3, 2008

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.