git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: git <git@vger.kernel.org>
Subject: git diff-files weirdness (bug?)
Date: Fri, 23 May 2008 15:20:47 +0100	[thread overview]
Message-ID: <b0943d9e0805230720h61cbabbbw180908e1b28a34cc@mail.gmail.com> (raw)

Hi,

I was investigating a bug in "stg refresh" failing with moved files
and noticed that it was caused by Git (HEAD pulled yesterday):

  git init
  touch a
  git add a
  git commit -m "test"
  git mv a b

These are OK:

  git diff-files -- a
  git diff-files -- b

These fail:

  git diff-files -- a b
  git diff-files -- a c

These are OK:

  git diff-files -- a b c
  git diff-files -- a b c d e
  git diff-files -- c d e
  ...

It looks like the two arguments command is a special case. Passing
"-q" doesn't make any difference.

Thanks.

-- 
Catalin

             reply	other threads:[~2008-05-23 14:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-23 14:20 Catalin Marinas [this message]
2008-05-23 16:14 ` git diff-files weirdness (bug?) Linus Torvalds
2008-05-23 16:50   ` Linus Torvalds
     [not found]     ` <7vbq2wsxnk.fsf@gitster.siamese.dyndns.org>
2008-05-23 22:49       ` [PATCH] diff -- file1 file2: do not default to --no-index inside a git repository Johannes Schindelin
2008-05-23 22:50         ` [ALTERNATIVE PATCH] diff " Johannes Schindelin
2008-05-24  7:25           ` Junio C Hamano
2008-05-24  7:25           ` [PATCH 1/3] tests: do not use implicit "git diff --no-index" Junio C Hamano
2008-05-24  7:26           ` [PATCH 2/3] diff-files: do not play --no-index games Junio C Hamano
2008-05-24  7:26           ` [PATCH 3/3] "git diff": do not ignore index without --no-index Junio C Hamano
2008-05-24  0:00         ` [PATCH] diff -- file1 file2: do not default to --no-index inside a git repository Junio C Hamano
2008-05-24  5:17           ` Junio C Hamano

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=b0943d9e0805230720h61cbabbbw180908e1b28a34cc@mail.gmail.com \
    --to=catalin.marinas@gmail.com \
    --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).