Re: Move using initial state
From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Mon, 9 Sep 2013 17:35:53 +0100 (BST)
Branko Čibej wrote:
> Julian Foad wrote:
Hmm, my comment about "makes it feasible" may have been unfounded: I agree that we could relatively easily implement a consumer that works efficiently with that scheme. In one possible implementation, purely for the purpose of illustrating whether I've understood correctly, the "delete" operation would not delete the subtree permanently until the end of the edit, and until then the subtree would merely be moved aside or hidden from the current view, but still able to be used as a move source, traced from a reference to its "initial state" path.
I still can't shake the feeling that it doesn't match the "sequential edit" philosophy. It seems to me that fundamentally "move away" is very similar to "delete" and yet we're proposing to accord it a special privilege. If we allow the edit driver to do that, then it feels like it should also be allowed to do things like create a new directory 'A/B' before creating the parent directory 'A' rather than the present requirement for doing everything in "build it up" order.
> I also don't agree that Ev2 design makes any assumptions about initial state.
Yes, I suspect you're right. /me tries to get over that.
This is an archived mail posted to the Subversion Dev mailing list.