>or
>

>git commit -a
>

>git will gather all changes and commit. Files not changed will not be touched.
>The same way is to get to an old state via git checkout.
>The idea is to get the whole state of the project at once
>There are ways to get single files too, but this is not for day to day work.

From my experience, not too good for VFP. Because of the files you may have touched and didn't actually change anything, but since they contain an ActiveX reference (or other COM), some kind of reference ID, a GUID or whatever in one of the field changes behind the scenes, and that marks the file as changed.
I know some versions of scctextX have the ability to ignore that (by not including that field in the first place), but I still don't think it's good enough.
I prefer to have granular control, i.e. to know exactly which files I'm committing, and in case of doubt (was this any change I made, what's going on here? and such) I'd force myself to doublecheck the differences before either checking in my version, or getting the repository version. On a team of 4-5 people, this reduced the number of snafus to one or two a year, which was great.
With any kind of blind reliance on timestamps, I'd expect that to be once a month at least.