pulling to another location results in "changed files" for big files

[shacharm2]

scenario:

1. clone to a different location
2. perform git pull and git bigstore pull
3. new files will marked as modified after the bigstore pull

Changes to be committed:
(use "git reset HEAD ..." to unstage)

modified:   bigfile.log

imho - just an unverified opinion - git compares the changed big file to the pointer file, where as it should compare the git big file's pointer itself.

It makes it unpractical to be used on any other location (or even same machine, different folder) - other than the original local git repo,