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

[RFC] git-diff-cache sans --cached and unmerged paths

From
Junio C Hamano <junkio@cox.net>
Date
May 2, 2005, 23:21 UTC
Message-ID
<7vr7gpnria.fsf@assigned-by-dhcp.cox.net>
Linus, 
    git-diff-cache without --cached says 'U filename" (or
"unmerged filename") when working with an unmerged cache entry.
Since the form without --cached is to mean "look at the work
tree", I think it should be changed to report the mode and the
magic 0{40} SHA1.  What do you think?

I was manually fixing up a merge and I wanted to compare the merge result in the work tree with the pre-merge HEAD version from either heads, but this behaviour (yes I am the guilty one) makes it cumbersome, and that is the reason behind this question.

BTW, when you have a chance, could you please give the executable bit to git-apply-patch-script, pretty please. This is my fourth attempt ;-).

Next: Linus Torvalds
Message 1 of 2 in “[RFC] git-diff-cache sans --cached and unmerged paths”
  1. Junio C HamanoMay 2, 2005
  2. Linus TorvaldsMay 3, 2005

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.