In this example, the "project_a" folder carries the mergeinfo property.
The commit hook complains that the operation is a merge an blocks (the user did not use the word "merge" in the message since the operation is no merge at all).
Doing the same rename in a working copy works.
I was not able to find any documentation on that behaviour: Obviously svn copies the mergeinfo property from the root folder to the renamed folder - but does only so if the rename is invoked as "svn rename from_url to_url". If the rename is applied to a working copy and commited afterwards, the svnlook on the server does not show adding the mergeinfo property.
I cannot imagine a case where copying the mergeinfo to the new folder is a wanted behaviour, even worse, without the user being able to notice anything about such an operation.
Maybe there's something wrong in our setup? Or is this the expected behaviour?
The server currently uses httpd 2.2 + svn 1.8.13, the clients used for testing where svn 1.8.13 and svn 1.9.7.
Re: svn rename adds mergeinfo property / renaming in working copy does not
On 07.11.2017 16:14, Nicolai Scheer wrote:
> Still, I can't get from the archives why a URL to URL rename does add
> mergeinfo, although the folder to be renamed does not have any
> mergeinfo props itself.
> But maybe I'm just not into the details why this can't be changed
Copying a directory is the same as creating a branch. You need the
mergeinfo in order to know what to merge. The recorded mergeinfo
describes the source path and revision of the branch.