On Feb 18, 2009, at 09:40, Theodore.Papadopoulo_at_sophia.inria.fr wrote:
> at my work, we use rsync to create backups of user data. In my
> case, 23% of the files are in svn checkouted directories unders the
> paths
> .svn/{tmp,text-base}.
>
> 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
However, this will check out the current revision of all files, and
not the revision you had before, which may have been older. If they
were older, attempting to check in from such a reconstructed
directory could result in work that had been subsequently committed
to the repository being undone, which is not what you want.
I would say that you should back up the entire working copy without
modifying or deleting anything in the .svn directories. If the point
is to preserve a developer's uncommitted work in the case of a
workstation crash (and there's no point using this method to preserve
committed work, since that's in the repository), then this is the
only way I know of to accomplish this today.
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=1187451
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-02-18 19:28:07 CET