[Monotone-devel] Re: wrapping up the changeset branch

[Daniel Phillips]

On Thursday 14 October 2004 11:17, graydon hoare wrote:
>    - introduces a new pair of abstractions: change_set and revision.

In the nit department: "changeset" has pretty much entered the language 
as a noun:

   
http://www.google.com/search?q=changeset&sourceid=mozilla&start=0&start=0&ie=utf-8&oe=utf-8

>      - a change_set is a blob of text containing:
>        - a path_rearrangement, which describes add/del/rename
>          operations on files, and del/rename operations on
>          directories - a delta_map, which describes edits made to a
>          tree after the path_rearrangement has been applied

And so exactly matches Arch's changeset definition...

>     - because a revision ID integrates its parent IDs, revisions
>       naturally form a DAG, in which each revision *includes* the
>       history of how it came to be, as part of its identity. this
>       makes certain operations faster -- the revision DAG is now a
>       matter of fact rather than something to infer based on trust --
>       but increases the rate of tree divergence a bit. the hunch is
>       that it will not increase divergence *much*.

Yes, and the exact divergence will generally be interesting to users.

> as far as upgrading databases goes: it is imperfect and a bit lossy,
> but it seems to work. please *please* keep a copy of your pre-upgrade
> database. the process degrades all previously recorded rename
> operations to delete/add events.

Just as a reality check, renames are recoverable in theory, aren't they?

Regards,

Daniel