Re: Importing history from Visual Source Safe

Hi Scott,

> Steve: A closer match is probably "externals"...

Subversion does have the "svn:externals" property that you can use to
link to code from other repositories. But there are some difficulties
with using this, see these issues in the issue database:

Issue 937: svn:externals should work with files as well as directories
    See also 1820
Issue 1167: Recurse through externs for a commit
Issue 1258: Tag svn:externals on copy
Issue 1336: svn:externals should allow relative paths
Issue 2009: import fails when svn:externals used

I think I would prefer to keep copies of all shared code in all the
respositories that need it, but you can (I think) use "svn import" to
pull shared code in without a lot of trouble, after you make any changes
to the common source code files.

Lee

> We have projects that hold "shared code" where bug fixes and
> enhancements are automatically distributed to all the projects sharing
> it. I think subversion will require a lot of manual merging to get
> the same effect.
>
>

-- 
+=========================================================
+ Lee Merrill    lee@bustech.com    919-866-2008
+=========================================================
Unless otherwise stated, any views presented in this email are solely those of the author and do not necessarily represent those of the company.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org