DVCS where ancestry is not part of the revision-id?

[Stefan Monnier]

> Git has another solution: create a replacement object (commit object,
> for example) and then have a replace table which is read by the usual
> user interface tools. The original object remains, only the user
> interface is doing the replacing. For example, when "git log" is
> displaying commits, it automatically replaces some of the commits with
> another by looking at the replace table.

That doesn't solve the problem of rebasing, sadly (the problem being
that people who tracked your branch before the rebase are left out in
the cold after the rebase, and forced to rebase above your new branch).


        Stefan