On Mon, 3 Jul 2017 17:38:49 -0500 "Edward K. Ream" <edream...@gmail.com> wrote:
> > I wonder if some variation of the above was what caused the problem > in the first place - the possibility I only just thought of being "No > to all" when "Yes to all" was more appropriate. Wondering if that > could cause both branches to have the same hash, and lead to them > collapsing together. > > Git would be broken if that were true. I'm not sure about that cat .git/refs/heads/master 7a4b4c25e476c259c503cb3176c94d8fef3ea116 cat .git/refs/heads/sqlite-format 1672fac87b1001d39ccfcbcc4a1774d0515cc39b so if a "No to all" / Save sequence made all the files the same, the hash of the files would be the same, so the refs would point to the same things. I would have thought that commit messages being part of the hashes would have avoided that, but certainly indirectly copying all the files from one branch to another should make things look very similar. 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
