bzr too slow

[Denys Duchier]

Martin Pool <mbp at sourcefrog.net> writes:

> Right, and you could possibly also have "rollback tasks", which are run
> if the transaction is cleaned up without being committed.

My own approach to this issue is basically the TransactionFS that I posted about
earlier.

The TransactionFS by itself does not guarantee that committing it will succeed
(perhaps things have changed concurrently, or perhaps you are exceeding your
quota, or perhaps you have rights, but the filesystem is so mounted that you
cannot exercise them (might happend e.g. with poetzl's bme, etc...)).

If really desired, a robust form of journaling can be implemented that addresses
these issues, but that's a lot of work for basically NO reward (considering that
"bzr revert" can fix most practical cases).

Cheers,

--Denys