Check for modifications shows confusing list of modified properties after merge

Okay, looks like we start to understand more but still are confused:

It's not the text status which is modified, it's the property status.
And it was not the update command but the merge command who did change
the
property status. So we had been misleaded as we did not check for
modifications
between these both operations.

I understand that if I merge a 'source' folder with another 'source'
folder, the source folder
may have a change of its 'svn:mergeinfo' property. I would also
understand, that all
effected files of that merge may get a change in its 'svn:mergeinfo'
property,
although this would sound ineffective to me.

What I do not understand: We merge a revision with two files changed
and get about 20
files which are absolutely unrelated to that merge changed in its
'svn:mergeinfo' property ???
Why these 20 extra changes. Why not all, why not none?

* Is this as intended or do we do something wrong?
* Do we have to commit all these property changes?
* Should http://subversion.tigris.org/merge-tracking/design.html
explain it all or are there better
   explanations (will try to understand that tonight)?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_tortoisesvn.tigris.org
For additional commands, e-mail: users-help_at_tortoisesvn.tigris.org
Received on 2008-08-26 17:20:04 CEST