Re: mirroring and pushback of copies

On Wed, Jul 27, 2005 at 06:43:34PM +0200, Georg-W. Koltermann wrote:
> 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.

This is a known issue. copies are not preserved across smerge (psuh as well)
this is due to lack of svn api for generating delta calls
between trees while respecting copies.

I am thinking about working around this for some mostly used cases.

For now, it's recommended to mirror the whole tree, while branching
at project-level, ie, cp //mirror/project/branches/foo //local/project-foo.

> 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?

No it doesn't, while it does require read access to the repository root.

Oh, perhaps that's because you are mirroring and merging to the remote root?

Cheers,
CLK