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

(At first sight) unexpected git-diff behavior

From
MKMatthias Kestenholz <lists@spinlock.ch>
Date
Jan 27, 2007, 08:42 UTC
Message-ID
<1169887333.19364.10.camel@localhost.localdomain>
Hello,

I often specify revision ranges when I need a diff, because I find it easier to see what is diffed against what:

git diff v1.5.0-rc0..v1.5.0-rc1

Today I tried to do the same to get a diff between linux v2.6.11 (which is a tag for a tree object) and v2.6.12:

$ git diff v2.6.11..v2.6.12 error: Object 5dc01c595e6c6ec9ccda4f6f69c131c0dd945f8c is a tree, not a commit fatal: Invalid revision range v2.6.11..v2.6.12

Of course, git diff v2.6.11 v2.6.12 works as it should.

I am not sure if git diff should be able to work with tree objects in revision ranges (which does not really make sense).

Thoughts?
Message 1 of 1 in “(At first sight) unexpected git-diff behavior”
  1. Matthias KestenholzJan 27, 2007

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.