[RFC] history editing vs history presentation

Stephen J. Turnbull stephen at xemacs.org
Wed Jun 10 05:19:30 BST 2009

Maritza Mendez writes:

 > 1. Allow bzr-init to set a non-revocable policy (property of a format) when
 > a branch is created about whether (and what kinds) of history editing will
 > ever be allowed on that branch.  This sounds simple but might not be.
 > Checkouts would have to inherit from their parents I think, and successively
 > unbinding and rebinding might cause ugly edge cases.

It's much worse than that.  See the monotone documents mailing list,
and discussions of authenticating/auditing git repositories.

Basically, you have to require signatures on commits.

More information about the bazaar mailing list