>>Marco,
>>
>>As I expressed in the other message. PE is implementing git in a per-file way of thinking. While it is possible, it's the wrong approach to git.
>>git is in snapshots of the whole project rather then check out / check in of (or: dealing with) single files.
>>
>>The right way using git is commit all changes done per task (as atomic it might be is up to the user).
>>Just
>>

>>git add .
>>git commit
>>#short :
>>git add .; git commit
>>

>>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.
>>
>>One might show the state of git status per file on an IDE - but this is mostly superfluous. Looks nice - means nothing.
>>Just running the commands above will commit recent state - or, in case nothing is changed, exit without notification.
>>
>>If one dislike command line then some git-GUI might be helpfull - but it all end in click this - click that to replace a single line of command - what could be called with VFP's RUN from command window.
>>I strongly recommend to Pro-git and understand git rather then learning in GUI first.
>
>I can't tell for sure if there's no auto / manual commit setting - just starting to read the awesome documentation -
>but sure it would not be a big deal to add that option.
>
> On the other hand, auto commits can be very useful - and of no strange usage.

It's a good idea to understand git first - it's not like VSS or similar SCM.
For an 'nix based project, git documentation is like a charm, even git help some_command shows something usefull. And as soon as one can address a problem. one will find a solution on the web.
Pro Tip: if you are playing around, use the bash that ships with git for windows. Most help will not be on cmd or similar MS wonders.

I'm on the strong side to not put binaries (table based sources) into the repository, but this is not everybody taste. And it has own quirks. Anyway, FoxBin2Prg is a great tool. I will push out my fork those days, it comes with some ideas about git and the Fox. Just reworking the change list.