The documentation had a paragraph near the end:
<<<
So instead, we'll create a *second*seaoe transaction, representing the
target of the update. In the plain update case, this transaction is
an exact copy of the revision (and perhaps we'll optimize out the txn
and just use the revision tree after all). But in the disjoint subdir
case, this second txn will also reflect the disjointedness. In other
words, when a disjoint directory D is discovered, it will be linked
into both txn trees -- in the reflection txn, D will be at whatever
revision(s) it is in the working copy, and in the target txn, it will
be at the target revision of the update. This way, the delta between
the reflection and target txns will apply cleanly to the working copy
(i.e., svn_repos_dir_delta() will just Do The Right Thing when invoked
on the two txns). Voila.
>>>
What happens if I do:
svn checkout http://svn.collab.net/repos -d svn
# note the lack of "/trunk"
cd svn/trunk/subversion/libsvn_fs
svn switch http://svn.collab.net/repos/branches/blue/subversion/libsvn_fs
I figure now I have two copies of libsvn_fs from the blue branch, one being
the original, and one being disjoint. What behavior will be seen in the
various permutations of modified/unmodified on the two copies when an update
is performed?
Sincerely,
Jay Freeman (saurik)
saurik@saurik.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:59 2006