RE: Re: Automate backup of working copy

> Mind if I ask why don't you change your working habbit and create a feature branch for this kind of work, commit it regularly and at the point it's ready for trunk (or the production version) reintegrate the
feature branch?

Not at all ...
I guess it comes down to procedure / habit / commit policies etc.

Not that these are set in stone, but I'm a great believer in computers being here to make our lives easier. Whilst I develop code to make my customer's lives easier, I think of things that could be done to make it easier to do my job.

I don't like maintaining more than one version of a piece of code and branching means potentially working with another version of the same code - so I tend to avoid it.

If TSVN can't do it - and I didn't think it could - I'll have a quick hunt for folder sync'ing options that are aware of svn status. I could always just sync the files (excluding .svn folders) to a cloud sync'd folder with rsync -C ..

Time for some thought over the weekend, I think.

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3180617

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2016-07-29 17:52:43 CEST