File history with VSTS API about vsts-rest-api-specs HOT 1 OPEN

VSTS currently needs to resolve the path at the tip commit so we can get the exact casing for the path and canonicalize it (i.e. convert "a\b.txt" to "a/b.txt", unless there is actually an item named "a\b.txt"). The underlying file history algorithm is case-sensitive and assumes exact paths but humans are really bad at typing exact paths.

We could probably just fall back to using the path verbatim if it doesn't exist at tip. I'll pass this on.

Note that this behavior isn't technically specific to renames or --follow. core/official/upstream "git log" works for files deleted at tip even if you don't use --follow

mkdir del
cd del
git init
echo a > a.txt
git add .
git commit -m a.txt
git rm a.txt
git commit -m del
echo b > b.txt
git add .
git commit -m b.txt
git log -- a.txt <- shows history of a.txt even though its deleted
git log -- A.txt <- empty history (it's case sensitive, as I would expect, even w/ core.ignorecase=true)

from vsts-rest-api-specs.