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

Re: Best Practices question

From: Peter Davis <peter_at_pdavis.cx>
Date: 2002-10-09 23:18:07 CEST

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 09 October 2002 08:20, Wolf Josef wrote:
> Sometimes unrelated projects grow together. Is there any way
> to merge them afterwards?

As long as the merging takes place in separate directory trees, you can use
svn's version of CVS modules.

Set the svn:externals property on a directory to checkout directories from
other repositories whenever the original directory is checked out. The
repository remains separate, but in the working copy it appears that they
have been merged. If you commit to the imported directory, it will affect
the external repository.

The merge isn't completely clean: the import only affects working copies, so
you won't be able to use a URL in the first repository to access modules
imported from the second. They remain separate URLs.

Or, you can do the svnadmin dump trick, which will completely merge the repos,
but is a little more difficult.

- --
Peter Davis
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9pJ0PhDAgUT1yirARAnBNAJ9MOVF4zbLn1DgE9q0okqsfOUlgvgCdFHqF
7gZniFM48/jnPYfhZo+acUw=
=xNPR
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 9 23:18:49 2002

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

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