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]] $path should probably not expect the
same, so the following still works.

cp COPYING COPY
git blame -C -C -C COPY

Btw, why isn't -C -C -C the same as -CCC? Should it?
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


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 case sensitive, like FAT.
For example, if a directory listing finds makefile when git expects 
Makefile, git will assume it is really the same file, 
and continue to remember it as Makefile.

So various workarounds does _not_ mean that _all_ filenames are processed 
modulo upper/lower case, or?


---
Thomas
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


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
 expects Makefile, git will assume it is really the same file,
 and continue to remember it as Makefile.

 So various workarounds does _not_ mean that _all_ filenames are
 processed modulo upper/lower case, or?

Keywords in that paragraph include various (not all) and better
(not perfectly), and the most important one is when git expects.

When running git add file.txt with File.txt in the index, git
expects File.txt, but the ignorecase logic makes git assume they
are the same, and add content from file.txt as File.txt.

And git blame $path probably should expect $path is something that
appear in the tree of HEAD; apparently it does not.

Patches welcome.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html