Daniel Carrera <[EMAIL PROTECTED]> writes: > Lapo Luchini wrote: >> Alex Sandro Queiroz e Silva wrote: >>>> It looks like the closest thing, except that it keeps a >>>> history off the change and the undoing of the change. Is that right? Is >>>> that a feature? >> >> Yup, it's because it's "monotonic" in nature you can only add, never remove. > > > Does that have anything to do with why Monotone is called Monotone?
No, not really. The original idea (IIRC) was that "monotone update" would always give you a tree that was no worse than the one you had before. So you'd have a tree that was monotonically improving in some useful sense (or at least non-decreasing in quality). _______________________________________________ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
