RE: Automate backup of working copy

David Balažic comments

> Sometimes developers leave uncommitted files in their WC when they leave at the end of the day.
> Regardless what branch(es) they use.
>
> If the PC dies during the night, work is lost.
> Regular backups help, but as most of the WC is in the repository, backing up the entire WC "wastes" backup space.

I use command-line "svn diff > backup-file-path.patch" (with the backup file path name on a separate drive). That saves the edits in my working copy, including any new files provided I've remembered to svn add them. The command is light-weight enough to run several times a day if feeling nervous.

It's not perfect, but it saves 90% of the effort needed to re-create work after a working copy loss. Set up a new working copy and use TortoiseSVN to apply the patch from the backup drive. This doesn't cover property or significant tree-structure edits very well, but it copes all right with text edits and additions.

 - Mark Irving

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

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2016-09-14 15:29:28 CEST