Large svn external
Posted
by MPelletier
on Super User
See other posts from Super User
or by MPelletier
Published on 2010-04-14T13:46:03Z
Indexed on
2010/04/14
13:53 UTC
Read the original article
Hit count: 594
I have a project which uses a large library residing in its own repository.
Using: Tortoise-SVN, the server is running an enterprise edition of VisualSVN
The project itself has the "standard" structure:
- trunk
- tags
- branches
In each branch, tag, and trunk is the library, set as an external (svn:external property). If I get the entire tree, I get the library several times, which is just getting too ridiculously repetitive.
Is there a recommended structure for this? Or perhaps a way not to get all externals (because other externals are much smaller, easier to manipulate)?
© Super User or respective owner