Inconsistent File/Directory name case causes problems about git-tfs

[spraints]

I've noticed the case problems before. I thought that clone/fetch worked around this.

How did you create your repository? with clone or quick-clone?

[mpareja]

This happens when fetching, cloning and quick-cloning.

When I tested the quick-clone I noticed there were fewer number of untracked directories in this case. I suspect the casing was fixed during some earlier TFS checkin.

[spraints]

I asked because I don't think quick-clone does anything special to handle casing. So it wouldn't surprise me too much if quick-clone failed to get the casing right. fetch is careful to use consistent casing. clone uses fetch.

What version of everything (git, git-tfs) are you using?

[mpareja]

Here is the version I compiled with: 8aa9572.

[mpareja]

I believe this issue occurs when a single TFS checkin has inconsistent casing in it and there were no previous checkins for the same path to get the casing from. The method UpdateDirectoryToMatchExtantCasing uses the paths already in the tree when consolidating the case, but the items being added during the single commit are not included.

[spraints]

Since it's been 6 months, I'm closing this issue.

If you're still having the problem or you're interested in helping to track it down, please re-open this issue. If you do re-open it, I'd really appreciate more details about the problem, e.g. a git log --stat and/or change info from a series of TFS changesets that trigger the problem.

[spraints]

This should be fixed as of 1bd12c1.

[mpareja]

Great! I'll give this a go as soon as possible. (I never thought of using an invariant case string comparer, nice!)

[mpareja]

FYI - I verified this is no longer an issue.