I just migrated my files from the old PC to the new. That includes a few development git repositories.
But I guess because the files were copied, the datestamps are different, and so git is now seeing them as uncommitted changes, even though there are no other changes to the files.
What is the best thing to do about this, just commit the files or is there some git magic (commands) to tell git everything is OK?
TLDR: file copying repos and not git cloning them across different file systems (EXT4 vs NTFS/FAT32) will make git complain.
Full Answer:
When talking with a friend knowledgable in Git, he figured out the issue.
When migrating my data including the repo from the old PC which has a Linux file system to the new Linux PC, since I had no network connection, I copied everything onto a USB HD, which was formatted with a Window's file system, thus losing some file information and Git reporting everything had to be checked in again.
So the solution was to move the repo only over Linux file systems.
I set up a remote repo on a Linux file sever, pushed the local working repo from the old PC to the remote git server and then cloned the remote to the new PC.
Extra Points:
Cloning did not pull all of the remote branches. I found this solution for pulling all remote branches.
git-pull-all https://gist.github.com/grimzy/a1d3aae40412634df29cf86bb74a6f72
#!/usr/bin/env bash
git branch -r | grep -v '\->' | while read remote; do git branch --track "${remote#origin/}" "$remote"; done
git fetch --all
git pull --all
Thank you all for your help, your time and suggestions.