Ben Collins-Sussman <sussman@collab.net> writes:
> Well, if you ask me, I don't think it's 'essential' anymore, just
> something that's very nice. That's just my opinion.
>
> Once upon a time, it was absolutely critical that imported vendor trees
> be "related" to each other in the svn repository. If not, then 'svn
> merge' wouldn't work well when comparing the trees. That's why Blair
> wrote svn_load_dirs.pl: to forcibly create relationships between the
> vendor trees.
>
> But nowadays you could simply 'svn import' two vendor trees, and then
> run 'svn merge --ignore-ancestry'. You'll end up with a bunch of local
> mods to your working copy that are extremely similar to what you get
> when you run 'svn merge' onto "related" vendor trees.
How would you do this? I've never successfully imported a tree in the
same place twice -- I get weird error messages when I do it. (I
assumed that it was just the system's way of telling me I was not
supposed to use import twice for the same sources...)
> (Anyway, svn_load_dirs.pl *is* included in the tarball, along with
> zillions of other tools. They all live in the same tree. If the binary
> packager volunteers forget to include the script, then we should point
> that out to them.)
Thanks...
--
Perry E. Metzger perry@piermont.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Feb 24 21:29:01 2004