mirroring and pushback of copies

Hi,

I noticed some unanticipated behavior when mirroring and copying.  This 
is what I did:

# setup mirror
svk mirror /local/mirror/remotehost/repository http://remotehost/svn/repository
svk sync /local/mirror/remotehost/repository
#
# create local path for offline work
#
svk cp /local/mirror/remotehost/repository /local/repository
#
# create a branch locally (******* point X)
#
svk cp /local/repository/trunk /local/repository/branches/mybranch
#
# continue to work locally, using svn via file:///opt/svk/local (that's where
# my svk /local is mapped to), and make some changes to 
/local/repository/branches/mybranch
#
# now push back
svk push /local/repository
 

This did the push back, but when looking at the history of 
/branches/mybranch on the remote host, I found that any file at this 
place did not have any knowledge that it once was copied from trunk, 
i.e. the history stopped at point X above.

Q: Is there a way to push back the fact that I copied mybranch from 
trunk, i.e. the pushing back the equivalent of svk log -x ?

There was another surprise: I needed write access to the repository root 
at the remote site when pushing back.  Why is that? Is it to store a 
property containing the merge history on the remote?

--
Regards,
Georg.

smime.p7s
Description: S/MIME Cryptographic Signature