>There is a lot operation with files committing and clicking this and that in peoples mind. This is not VSS
>The idea is commit snapshots of the whole project. Once set up right a simple
>

>RUN "git commit -a"
>

>is enough in most cases

I don't think so. Git specifically separates Staging and Committing for this very reason. You choose files with staging and then commit. Whole project saving in real projects is the anti-thesis of good source code management unless you are extremely disciplined and only change relevant code directly related to an issue/work item. I know I rarely do that so I almost always selectively commit changes.

My process is commit small and commit often. Meaning small changes that address specific issues. This is a big reason as it limits the amount of potential merge conflicts. It also ensures if I f*ck up my code (as I often do when experimenting with new stuff) I can get back to something stable more easily.

I think this is common, so the 'entire project' approach is something I've not seen in practice.

But again, there's not one right way. THe same was true for SCC or SVN or CVS etc. Source control can be used in many different ways and still be useful in all of them.