"Bert Huijben" <bert_at_qqmail.nl> writes:
> How can you recover from this state?
> Can you delete the incomplete node? (It's parent?) or is the only way to
> recover to revert the root of the copy operation?
> If only that last case is true I wouldn't call it a defined database state.
I don't really understand the question. At present an interrupted copy
leaves working nodes in state incomplete. There is no way to complete
the nodes, other than reverting and starting the copy again.
What I propose is that copy only produces the incomplete state for nodes
that are copies (or copies of copies) of repository nodes. Copy would
not produce the incomplete state for copies of added nodes. When an
added node is copied the copy is an added note completely separate from
the source and if an interrupted copy causes it to have fewer children
this is not the same as the copy of a repository node having missing
So incomplete would mean "this repository node is incomplete" for base
nodes and "this copy of a repository node is incomplete" for working
nodes. It would not mean "some user operation was interrupted".
uberSVN: Apache Subversion Made Easy
Received on 2011-10-18 10:31:58 CEST