>>>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.
>>
...
>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

Could you go a bit into detail on your physical/net logical layout of repository location(s) used and your strategy for physical backup to put into bank vault(s)?
Archive, bundle, clone or do you use bare OS system tools from xCopy .Git Dirs up to more wholesale strategies wih like partition/drive cloning?

thx

thomas