Karl Fogel <email@example.com> writes:
> Ben Collins-Sussman <firstname.lastname@example.org> writes:
> > Indeed, this is the only real thing we can do, and it's a big "hunka"
> > server work, as you said. Specifically, it's a big hunka filesystem
> > work.
> > The client sends a tree-delta devoid of text-deltas; this tree-delta
> > gives a root revision #, and then "replaces" any file or dir which is
> > at a *different* revision #.
> > The filesystem then builds a mini-node-tree, floating in space, which
> > is a model of the working copy. The filesystem then compares this
> > tree to the "head" tree, and sends back a custom tree-delta.
> > Does everyone agree on this model now?
> It is a hunk of work for the repository, but it has the advantage of
> being extremely comprehensible for the humans who will have to work
> with it. Anyway, I can't think of another way to do it, though that
> might just be because I'm a human. :-)
Not having actually written code to do this, it doesn't sound too hard
at all. It maps directly onto the semantics of the operations we have
Received on Sat Oct 21 14:36:17 2006