Here is the present status of the various branches: - The one-node branch has been merged by hand into trunk. I took great care with the merge, and do not expect any problems on that account. The branch remains visible in leo-launchpad because I have not officially declared it merged, but no further work is planned in that branch.
- g.unified_nodes is False at present in the trunk, so using the trunk should be safe. - I made several changes to the 46-maint branch in contemplation of a Leo 4.6.3 release. It has become clear today that caching and clones don't mix. That is, clones in leoProjects.txt become the enemy of nodes in later @thin trees: they override the data in the external files! This is a serious data-management problem and must be fixed immediately. I would be shocked if this issue relates to the one-node code. Any such fix will be part of the 46-maint branch and thus the Leo 4.6.3 release. 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 -~----------~----~----~----~------~----~------~--~---
