>>>I'll be back in business in a few hours and I still think that I'm way ahead in time spent over the years.
>>>It does point out, however, how I have to accelerate my transition from VFP to .NET.
>>>This has never happened with text or XML source files.
>>
>>One time is enough. Heart misses a beat.
>>I have never killed a vcx based class hat way too. The git commit is not lower then a compile, I can bear it. Finaly on could automate it, so that it will run after a compile w/o any disturbance to compile / test at all.
>
>I think flooding with every change o each compile is too much - I prefer having only completed work sets - even if not totally debugged - in my ***local*** deposit. In (common) project only workable commits that will not disturb others, so as to not have to be careful of the fresh amount when synching/merging.
>
>So accustomed to that work flow that I use it even for single dev/multiple client library setups.
>
>>I use git for testing vfp tables, just setting them back to previous states with a one liner in command bash. Realy nice. Fast.
>
>There I usually go for a few (often compressed) directories, to be able to have different test data sets.

The good on git is that there is no "right" workflow

I do something like

-beeing on branch dev
-git checkout -b something_new
-now I flood git with my backups
-and on the commit where I like to have something meaningfull
-git checkout -dev
-git merge --squash --edit HEAD@{1}
-git branch -D something_new


this squashes all just-backup-commits to one meaningfull

The real good is that I can do an nice undo, and the tree is stll not flooded with commits