Tim Scott wrote:
> Sometimes I don't commit stuff to the repository, because it doesn't work yet.
> Sometimes that can take a while to get right - I might put the work aside whilst I
> work on something else.
> Sometimes there's a lot of work put into getting something written and it's
> nearly there, but not nearly ready to be releasable.
> This happened very recently. Just before a complete, total, fundamental and
> unrecoverable hard drive crash on my machine - there was no chance of
> recovering the files and the drive was encrypted.
> So I've lost a lot of work - in particular an intricate learning exercise I'd carried
> out trying out a new module with a new set of libraries ... but just wasn't quite
> there as it was flaky and only performed at about 2.5% of the speed of the thing
> it was replacing.
> Is there a way to have tortoise automate the backup of my working copy
> folders? This must include changed, deleted and unversioned files.
I'll chime in here.
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.
So I repeat (almost) the same question (in case someone figured out some solution):
Can the backup be persuaded to ignore files that are already stored on the SVN server?
A half solution is to ignore the .svn folder(s) in the backup process. (saving about 50)
Any other idea?
Currently I use Windows builtin file backup, but that could change.
The client systems are using Windows 7.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2016-09-14 15:09:50 CEST