Re: Merging 2 repositories

Mark Benedetto King wrote:

> Well, whether or not it should make this assumption is arguable, but the
> fact is that it does make this assumption.

Noted. I can see why it was done that way and short of a completely different
table structure I cannot think of a better way to handle it. I am willing to
live with it for my own purposes (since I know that the modules are completely
independent).

However, I have just thought of a better way to recommend doing the merge.
Don't merge the repositories at all for independent projects! Convert each
project into it's own repository, with all repositories being contained in a
common directory (so SVNParentPath can be used). Any projects which may need to
have files copied from another project should be stored in a single repository
and converted at the same time. QED.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org