On Mon, 3 Jul 2017 13:11:47 -0700 (PDT) "Edward K. Ream" <[email protected]> wrote:
> I am attempting to understand why code keeps changing unexpectedly. > > Clearing .leo/db does not completely solve all problems. It may be > that #505 should be reopened, but something stranger may be > happening. Perhaps pre-505 code remains in branches. Perhaps > something else. > > Until I figure out what is happening I recommend suspending *all* > work on Leo, even in branches. This is interesting: https://api.github.com/repos/leo-editor/leo-editor/events I think it confirms my impression that f0a76ae collapsed the branches together. I think this collapse could be caused by unintentional misuse of the `git reset` command, so if that happened it would explain things. Otherwise I'm not sure. Anyway, as long as no one uses git push --force, I don't think it's possible to lose anything. Cheers -Terry -- 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.
