{"thread":{"id":"6562","subject":"(At first sight) unexpected git-diff behavior","startedAt":"2007-01-27T08:42:13Z","lastAt":"2007-01-27T08:42:13Z","messageCount":1,"participants":["Matthias Kestenholz"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"32815","messageId":"1169887333.19364.10.camel@localhost.localdomain","threadId":"6562","inReplyTo":null,"subject":"(At first sight) unexpected git-diff behavior","fromName":"Matthias Kestenholz","fromEmail":"lists@spinlock.ch","sentAt":"2007-01-27T08:42:13Z","receivedAt":"2007-01-27T08:42:13Z","isPatch":false,"sender":{"key":"lists@spinlock.ch","avatar":null},"body":"Hello,\n\nI often specify revision ranges when I need a diff, because I find it\neasier to see what is diffed against what:\n\ngit diff v1.5.0-rc0..v1.5.0-rc1\n\nToday I tried to do the same to get a diff between linux v2.6.11 (which\nis a tag for a tree object) and v2.6.12:\n\n$ git diff v2.6.11..v2.6.12\nerror: Object 5dc01c595e6c6ec9ccda4f6f69c131c0dd945f8c is a tree, not a\ncommit\nfatal: Invalid revision range v2.6.11..v2.6.12\n\nOf course, git diff v2.6.11 v2.6.12 works as it should.\n\nI am not sure if git diff should be able to work with tree objects in\nrevision ranges (which does not really make sense).\n\nThoughts?\n"}]}