On Wednesday, June 21, 2017 at 8:25:34 AM UTC-5, Edward K. Ream wrote: These changes should be benign: added comments, new keys to g.Bunch's, etc. >
Wow. Changes made in master are "bleeding" into the new-read branch, probably as the result of the evil "last clone wins" rule. This is intolerable, especially since Leo does *not* report the unexpected changes in recovered nodes. Oh, the irony. Otoh, it shows that my strategy of switching between the master and new-read branches is an effective, if eccentric, test strategy. Yes, I could use yet another branch as a test bed, but with your indulgence I'll not do that. This horror show probably affects me the most, since I probably use clones the most. I'll devote all my programming time to fixing #505 asap. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
