Re: Aw: Re: git blame shows wrong Not commited yet entries

2012-09-01 Thread Martin von Zweigbergk
On Fri, Aug 31, 2012 at 10:58 AM, Junio C Hamano gits...@pobox.com wrote: And git blame $path probably should expect $path is something that appear in the tree of HEAD; apparently it does not. That probably makes sense. For anyone deciding to implement that, note that git blame -C [-C [-C]]

Aw: Re: git blame shows wrong Not commited yet entries

2012-08-31 Thread Thomas Ackermann
You are right but as I mentioned in my posting I am using core.ignorecase=true so I expected file.txt and File.txt to be treated the same. The man-page for git-config says: core.ignorecase If true, this option enables various workarounds to enable git to work better on filesystems that are not

Re: Aw: Re: git blame shows wrong Not commited yet entries

2012-08-31 Thread Junio C Hamano
Thomas Ackermann th.acke...@arcor.de writes: The man-page for git-config says: core.ignorecase If true, this option enables various workarounds to enable git to work better on filesystems that are not case sensitive, like FAT. For example, if a directory listing finds makefile when git

git blame shows wrong Not commited yet entries

2012-08-30 Thread Thomas Ackermann
Hi, I am using MsysGit 1.7.11 on WinXP 32 bit and experience the folllowing strange behaviour: For a file like File.txt in the repo, git blame file.txt (note the lower case) shows Not commited yet for every single line in the file. git blame File.txt (correct upper case spelling) gives the

Re: git blame shows wrong Not commited yet entries

2012-08-30 Thread Junio C Hamano
Thomas Ackermann th.acke...@arcor.de writes: I am using MsysGit 1.7.11 on WinXP 32 bit and experience the folllowing strange behaviour: For a file like File.txt in the repo, git blame file.txt (note the lower case) shows Not commited yet for every single line in the file. git blame