merge-tracking: Intentional reading of merge info outside a BDB transaction?

Today, I was poking thru the BDB code, and noticed the new public FS APIs
for merge tracking. As I dug into them a little bit deeper, though, I saw
something that didn't seem quite right: base_txn_merge_info() doesn't wrap
its read of the txn's proplist in a BDB transaction. Was that an
intentional deviation from the way svn_fs_base__txn_proplist() works (even
though the two are super-similar in functionality)?

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