Hello: I recently came across https://issues.apache.org/jira/browse/SVN-516 and am wondering if there is still interest in this due to the last commit being in 2016.
My interest in this stems from wanting to *archive* older commits that are unlikely to be accessed to an external disk or other medium, and then free up the space on the server. That way it still adheres to the principle of an unmodified history, just with less immediate accessibility. Note that I want to preserve the UUID and revision numbers so a dump/load cycle is not as favourable as this feature would be. I have an rough idea of how this may be done but I have never touched SVN source before and struggle to figure out what APIs would be relevant to the FSFS structure I found ( https://svn.apache.org/repos/asf/subversion/trunk/subversion/libsvn_fs_fs/structure) and am not sure I have room in my life to implement it at this time. My idea is, when packing a shard to also squash (similar to GIT squash https://git-scm.com/docs/git-merge#Documentation/git-merge.txt---squash) the commits together for a smaller delta. Remember that while this history is "lost" in the squash, it is supposed to have been archived elsewhere that enables it to be restored. The ability for shards to live on a different mount and soft-linked seems like a nice workaround for disk space, but that requires that everything is always mounted. Is there still interest? Is my implementation idea worth effort (in the future)? ~Matthew J.Turner
