All of lore.kernel.org
 help / color / mirror / Atom feed
From: Semyon Kirnosenko <semyon.kirnosenko@gmail.com>
To: git@vger.kernel.org
Subject: [BUG] diff and blame difference
Date: Tue, 26 Jul 2011 18:10:05 +0400	[thread overview]
Message-ID: <4E2ECABD.7050601@gmail.com> (raw)

Hi.

Again, I have to post about diff and blame difference problem.
The initial discussion ends here:
http://permalink.gmane.org/gmane.comp.version-control.git/165012

I have the same problem and now it's about non-whitespace lines. The 
problem is some line is marked in diff as added, but in blame it is 
marked as added in some older revision. And vice versa line is not 
marked as added in diff but it is marked in blame. Here are several 
examples from git repo:

Diff error in revision 198b0fb635ed8a007bac0c16eab112c5e2c7995c in file 
date.c.
Line 184: added in diff, but blame say otherwise.
Line 215: added in diff, but blame say otherwise.
Line 219: added in diff, but blame say otherwise.
Line 259: added in diff, but blame say otherwise.
Line 260: added in diff, but blame say otherwise.
Line 193: not added in diff, but blame say otherwise.
Line 212: not added in diff, but blame say otherwise.
Line 222: not added in diff, but blame say otherwise.
Line 300: not added in diff, but blame say otherwise.
Line 315: not added in diff, but blame say otherwise.

To get diff and blame i've used the following commands:
git --git-dir=D:\src\git\.git diff-tree -p 
198b0fb635ed8a007bac0c16eab112c5e2c7995c -- date.c > diff-tree
git --git-dir=D:\src\git\.git blame -l -s 
198b0fb635ed8a007bac0c16eab112c5e2c7995c -- date.c > blame


I have sent this before, but did not receive any response. I just need 
some type of answer. Something like "we will fix it" or "we don't care 
about it".

             reply	other threads:[~2011-07-26 14:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-26 14:10 Semyon Kirnosenko [this message]
2011-07-26 19:25 ` [BUG] diff and blame difference 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=4E2ECABD.7050601@gmail.com \
    --to=semyon.kirnosenko@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.