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

Re: Subversion working copy speed

From: Ulrich Eckhardt <eckhardt_at_satorlaser.com>
Date: 2005-08-21 15:36:32 CEST

On Saturday 20 August 2005 21:42, Robert Cronk wrote:
> 2. Source(un)Safe shared (or linked) files. Some other developers who
> currently use Source(un)safe use shared files or linked files which are
> similar to hard links on linux, so they can include a file into their own
> directory structure. I find this to be a hideous practice but I want to
> find out what will happen if we export our Source(un)Safe database into
> subversion. We are planning on stopping the shared file practices ASAP but
> I'm just curious about the conversion process.

There is a separate project called vss2svn which does this conversion. Since
there is no way for Subversion to handle these shared files, it will handle
them as separate files that just coincidentally happen to be changed
Other than that, a few alternatives:
- Use svn:external, for folders only though.
- Create libraries, depends on your setup if that is possible.
- Move the related projects into one folder, which has the additional
advantage that the shared files are testable for the other project without
first committing a (possibly broken) file. Also the chance is much higher if
both projects are in the same dir.
- Create shared files in a central location, copying them over whenever
updating a project. SVN makes these copies cheap and changes here won't
accidentally break other code there.

Just wondering: could I use the fourth method above and then set the copy to


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Aug 21 15:40:53 2005

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.