On Feb 18, 2009, at 14:23, Reedick, Andrew wrote:
> Ryan Schmidt wrote:
>> On Feb 18, 2009, at 09:40, Theodore.Papadopoulo_at_sophia.inria.fr
>>> At first glance, it seems silly to backup all those files that can
>>> be recovered from the repositories. Unfortunately, I have not found
>>> a way of re-creating the files under text-base from the proper
>>> revision stored in the file .svn/entries
>>> Is there a way to do that ?
>>> Is it safe to assume that with little work (eventually to be done),
>>> it would be safe to not backup those files ?
>> If they are deleted, you can get back the files in the .svn directory
>> by checking out over the top with the force option, which is new in
>> 1.5, I believe.
>> svn checkout --force repository-url existing-directory
> Wouldn't svn move/rename commands issued in the workspace be
> unrecoverable without the original .svn directories? So if a
> refactored some code and changed a few classnames/filenames, a 'svn co
> --force' would require the developer to pick through the file tree and
> re-issue svn add/mv/del commands on a per file basis.
Yes, that too. Basically, the developers work will be backed up, but
not in a way that could be committed back to the repository without
some extra work that you would avoid if you backed up the entire
working copy. And your developers' time is (hopefully) worth more
than the cost of an extra disk to store the extra data the working
copy brings with it.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-18 21:49:11 CET