Julian Foad <julianf...@btopenworld.com> writes: > [[[ > $ svn propget p $REPO/trunk -r5 > v > > $ svnmucc -U file://$PWD/repo -m "" propset p v trunk > r6 committed ... > > $ svn diff --summarize -c6 $REPO > [no output] > > $ svn log -vq --xml -r6 $REPO > <...> > <path > kind="dir" > action="M" > text-mods="false" > prop-mods="true">/trunk</path> > <...> > ]]] > > This output says that there was a property "modification" in r6 > ... and yet shows no changes.
The diff output is partly a choice made by the client itself. If we operate on a non-root node: svnadmin create repo svn mkdir -mm file://`pwd`/repo/A svnmucc -mm -U put repo/format file://`pwd`/repo/A/f svnmucc -mm -U put repo/format file://`pwd`/repo/A/f svnmucc -mm -U propel p file://`pwd`/repo/A The diff reports that the server sends to the client include an open-dir for /A in -c3 and an open-file for /A/f in -c4. The diff reports have no equivalent of log's text-mods/props-mods but they do communicate that a new node was created. The diff client could choose to output some sort of "new node" message. 'svnlook changed' has behaviour that is somewhere between log and diff above: it indicates a change for for the text no-op -r3 but no change for the property no-op -r4. -- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*