'svn plist' peg-rev buglet?

Observed moments ago using a relatively recent trunk build:

$ svn plist -v svn-test-work/working_copies/log_tests-18/trunk_at_6
Properties on 'svn-test-work/working_copies/log_tests-18/trunk':
   svn:mergeinfo : /branches/a:3-11
/branches/b:10-13
/branches/c:15-16
/trunk:2-14
$ svn plist -v svn-test-work/working_copies/log_tests-18/trunk_at_6 -r6
Properties on
'file:///home/cmpilato/projects/subversion/subversion/tests/cmdline/svn-test-work/repositories/log_tests-18/trunk':
   svn:mergeinfo : /branches/a:3-5
/trunk:2

My recollection is that our peg-rev policy states that the default operative
rev when a peg-rev is explicitly provided is, in fact, that peg-rev. But
that ain't what's happening.

Is my recollection right (and the demonstrated behavior, therefore, wrong)?

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand