On Tue, 4 Jul 2017 09:29:01 -0500 "Edward K. Ream" <edream...@gmail.com> wrote:
> On Tue, Jul 4, 2017 at 7:46 AM, Xavier G. Domingo > <xgdomi...@gmail.com> wrote: > > I think from past experience that some git corruption could lead to > this > > kind of "surprises". In those cases, the "git fsck" command was > > essential to see the causes... > > > > ​Many thanks for this tip. Here are the results of git fsck: > > > dangling commit 64bf971d642270198302059061653ef62fea3d26 > dangling blob 5bdc0328e60da97c669950a397673f3ec97082fe > > I have no idea what this means. Time to google, and perhaps time to > do a git clone to restart everything. I don't think there's any particular red flag there, commits and blobs can dangle (sit around without a reference) until the garbage collector gets them, or, as you suggest, a fresh clone is used. For example git commit --amend might create dangling commits. 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.
