On 11.09.2013 20:09, Julian Foad wrote: >> Proposal: Resurrect keeping the old node-line IDs, iff >> (a) the copy source (or a parent) got deleted in the next revision >> (b) no copies of that node (or any parent) were added since the source rev. >> That should keep normal copying relatively cheap and still provide the >> special behavior for our "undo" use-case. > I think you mean that the user-level copy should do this automatically. > Perhaps so. That need not be implemented in the FS layer; the FS layer could > just provide the primitives necessary to implement it.
This actually breaks the semantics of "copy" for no readily apparent reason. It's much more interesting IMO to consider how such a concept would be presented in the UI. I'll just note that resurrecting deleted nodes is orthogonal to the issue of move tracking. It's moderately easily done in the current top-down DAG model, since "delete" simply means "remove edge from graph"; and it's also provided for in the metadata-ng design. -- Branko Čibej | Director of Subversion WANdisco // Non-Stop Data e. br...@wandisco.com
