Yeah, this should not happen. Py files should win over txt files by default.
Terry Brown <terry_n_br...@yahoo.com> wrote: >I thought it was save to ignore (i.e. delete without inspection) >recovered nodes nodes, but they just bit me. I usually revert *Ref*.leo >and *.txt when committing changes which should apply only to .py files, >I assume this can generate recovered nodes nodes if clones in the .txt >file get out of sync. with what they were cloning in the .py file? >Anyway some of my changes were reverted, and I'm guessing it was by the >wrong winner of a cross file clone race getting written. > >Is this not supposed to happen, so I should try and make a test case? >Or is it not true that it's safe to ignore (i.e. delete without >inspection) recovered nodes nodes? > >I see I missed reverting one of the .leo files (but perhaps >not the .txt file) on one commit, could that be the culprit? > >Cheers -Terry > >-- >You received this message because you are subscribed to the Google Groups >"leo-editor" group. >To post to this group, send email to leo-editor@googlegroups.com. >To unsubscribe from this group, send email to >leo-editor+unsubscr...@googlegroups.com. >For more options, visit this group at >http://groups.google.com/group/leo-editor?hl=en. > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
