Julian Foad wrote on Tue, 09 Jan 2018 13:31 +0000: > Anyway the main point here is: we have in principle a set of tree > snapshots (no matter that each one is stored in the form of a difference > against the base); and we use revision specifiers to refer to the > working and base versions: ... > The big advantage of some (any) such scheme is that existing > libsvn_client APIs for operating on a working copy change or state (such > as cat, diff, status, prop*, revprop_get, revprop_set, etc.) can then > potentially be extended to support operating on a shelved change or > state without any change to the API function declaration itself.
This resembles the FS API, where svn_fs_root_t can be either a revision root or a txn root.
