git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthias Kestenholz <lists@spinlock.ch>
To: git@vger.kernel.org
Subject: (At first sight) unexpected git-diff behavior
Date: Sat, 27 Jan 2007 09:42:13 +0100	[thread overview]
Message-ID: <1169887333.19364.10.camel@localhost.localdomain> (raw)

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?

                 reply	other threads:[~2007-01-27  8:42 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1169887333.19364.10.camel@localhost.localdomain \
    --to=lists@spinlock.ch \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).