Hey Ryan,
Thnx for the answer, I posted the question and forgot to check (was hopeing for a mail :-s) Anyway we found a some-what other solution, we just dump the DB to our local-DB-server that we work, and put all info except the assets/files and assets/sessions in our git repo. With the script to import the DB we also copy the info from assets/files from the live location.
This way our clients can work with the live enviroment, we can import all the live-data to our local computers and work at it this way.
Only two 'real' downsides are that 'stuff' that gets thrown away in the live enviroment in assets/files isn;t deleted localy and the fact that if you change something in your local database / back-end you need to 'redo' that or do it on the live enviroment and then dump the DB back (or we can also dump our local DB to the live enviroment, but you need to be super-carefull with that offcourse)