[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Externalize .svn directories

From: Bolstridge, Andrew <andy.bolstridge_at_intergraph.com>
Date: Mon, 29 Jun 2009 08:58:02 +0100

> -----Original Message-----
> From: Jochen Wiedmann [mailto:jochen.wiedmann_at_gmail.com]
> Sent: Monday, June 29, 2009 7:08 AM
> To: users_at_subversion.tigris.org
> Subject: Externalize .svn directories
> Hi,
> I'd like to put a directory into subversion, which is controlled by a
> server. Users are modifying the directory via the server.
> The problem is, that the server barks, if it detects .svn directories.
> I can't have them in place. A solution for me would be, to have the
> .svn directories in a separate tree, each of them referencing to the
> actual directory. Is that possible? Has someone developed a
> workaround?

There is a workaround while you're waiting for wc-ng. Regularly copy the
server's directory to a different directory, and version-control that
copy. I do this for a separate system - every so often, I grab all files
from a dir and copy them on top of my WC. I can then see what files have
changed and can commit them all in one go. You could do this a little
more accurately if you could force a copy to happen when the server
changes something, or just run it hourly.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-29 09:59:04 CEST

This is an archived mail posted to the Subversion Users mailing list.