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

Re: git diff bug?

From
Célestin Matte <celestin.matte@ensimag.fr>
Date
Jun 6, 2013, 21:42 UTC
Message-ID
<51B10236.2030009@ensimag.fr>
In-Reply-To
<CANd8icJ_1mqT9m-n3wPPdjzG1oNjwxfQeUA6YL6KVxbq0iEa1g@mail.gmail.com>
Le 06/06/2013 23:26, Sarma Tangirala a écrit :
Show 7 quoted lines
> Hello All,
> 
> If I did 'git diff HEAD^..HEAD -- file' should git not report some
> kind of warning if it could not match the file? For example, if 'file'
> were infact 'dir/file' and 'file' were unique, would it not be a good
> idea to report that in the present working directory 'file' were not
> found but 'dir/file' were a match?

I don't know any program doing such a thing, and I don't think it is the role of the program to predict which file the user actually wanted to provide in the command line. That would imply looking for files with the same name or a close name in the current directory and its subdirectories - and maybe even in the superdirectory? It is hard to decide when you have to stop looking for the file.

Previous: Sarma TangiralaNext: Junio C Hamano
Message 2 of 6 in “git diff bug?”
  1. Sarma TangiralaJun 6, 2013
  2. Célestin MatteJun 6, 2013
  3. Junio C HamanoJun 6, 2013
  4. Sarma TangiralaJun 7, 2013
  5. Célestin MatteJun 10, 2013
  6. Sarma TangiralaJun 10, 2013

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.