On Wed, Dec 14, 2011, at 06:36, Eric S. Raymond wrote:
> Daniel Shahaf <d.s_at_daniel.shahaf.name>:
> > Replace requires a node to already exist at the target path.
> > Add requires a node to not already exist.
> OK, when you say "require", what do you mean? Just that if these conditions
> fail the node should not be modified?
If these condition fail I believe 'svnadmin load' aborts without
committing the revision they appear in (but with prior revisions having
already abeen commited)
> > (container == node)
> I see what you mean, but I think this is misleading terminology. The thing
> you are calling a "container" is a history containing a sequence of actions
> each one of which is *described* by a node.
Sorry, no. I said "node"; what you call a "node" is termed "node-
revision" in the FS.
> IMO the term "container" isn't a win either; it doesn't convey a
> strong enough sense of continuity over time.
> In the draft I'm working on, I've used the term "flow", and defined a
> flow as a sequence of actions on a path.
Received on 2011-12-14 13:35:38 CET