On Mon, Aug 2, 2010 at 11:10 AM, thyrsus <[email protected]> wrote: > LeoPy.leo or LeoPyRef.leo are not the leo files I'm concerned about. > I want to collaborate with my colleagues on the forests of system > configuration I maintain, and we are frequently committing to our > (internal) repository.
In that case, using @thin or @auto external files seems like the best way. > The "Recovered Nodes" give me hope that a humanly useful > representation of changes is possible. I need to study that code. > The result is so much better than opaque XML operations. The code is quite simple, because it is diffing body text, not xml. I would be very interested in a clearer representation of diffs, but I don't have a lot of hope. Even bzr qdiff, good as it is, often fails to convey the true nature of changes. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
