git-fsck isn't something you need to really worry about unless something goes bad in your repo. Dangling commits are commits that cannot be reached from any current branch or tag. They're very common, rebasing or amending commits will create them. git-gc, which is run automatically by various commands, will clean out old dangling commits for you. It keeps them around for some time (one month?) so you can retrieve them if you make a mistake. --tek
On Thu, Oct 9, 2008 at 9:59 AM, Lemur <[EMAIL PROTECTED]> wrote: > > Hi. > What is suggest to me when I have output with derective #git-fsck > like this: > git fsck > dangling commit 75d0afbe36bcd1f21c > dangling commit 501895315214b116 > > Thanks. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
