The fs-successor-ids branch adds successor ids (effectively, copyto
information) to the BDB backend. It hasn't touched libsvn_fs_fs or
libsvn_fs yet.
Has design of this feature for FSFS been discussed at all? I couldn't
find anything in the archives.
I suggested yesterday on users@ to create a new hierarchy (parallel to
revs/ and revprops/) and to store information regarding the successors
of /path/to/f...@rn023 somewhere under $new_hierarchy/N/N023/** --- where
'somewhere' is to be defined. (I have some unfinished thoughts about this.)
Also, I haven't seen the successor-ids during upgrade considered. Do we
consider the successor ids ('successors' table, or $new_hierarchy/) just
a cache of derived information (like node-origins), or does it have to
be retroactively-populated at the time of and by 'svnadmin upgrade'?
