-----Original Message-----
From: Mike Crowe [mailto:mac@mcrowe.com]
>> I have to ask, though: why are you backing up working copies? By
>> definition, they're meant to be scratch areas, "temporary"
workspaces.
>> It's the repository that really needs to be backed up.
>People are likely to keep changes in their checkouts for a number of
days
>before checking them in. These changes need to be backed up.
In our process (windows world): work is done on a local drive that is
not backed up. Developers are not allowed to commit work in progress
that does not build with 0 errors and 0 warnings and pass Build
Verification Tests. Developers use the TortoiseSVN "Create a Patch"
feature to create patch file of all changes and store the patch file in
their sandbox on a networked drive that is backed up nightly. The Idea
is to not lose more than a day's work, and to only backup changes not
the entire workspace and to not bloat the repository with lots of
personal branches by using it as a temporary sandbox. Maybe you could
do something similar?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 24 22:01:47 2004