{"thread":{"id":"13972","subject":"gc and empty packed-refs","startedAt":"2008-06-15T23:27:12Z","lastAt":"2008-06-15T23:27:12Z","messageCount":1,"participants":["Allan Wind"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"79994","messageId":"20080615232712.GA28979@lifeintegrity.com","threadId":"13972","inReplyTo":null,"subject":"gc and empty packed-refs","fromName":"Allan Wind","fromEmail":"allan_wind@lifeintegrity.com","sentAt":"2008-06-15T23:27:12Z","receivedAt":"2008-06-15T23:27:12Z","isPatch":false,"sender":{"key":"allan_wind@lifeintegrity.com","avatar":null},"body":"So I ran `git gc` as a user with group write access to my repository, then\nnoticed that remote clients complaining:\n\nallan@vent:~/var/git/www$ git pull\nYou asked me to pull without telling me which branch you\n...\nallan@vent:~/var/git/www$ fatal: The remote end hung up unexpectedly\nfatal: The remote end hung up unexpectedly\n\nwhich appears to be related to the packed-ref file being empty (as well \nas info/refs) on the server.  I copied the two files from my client to\nthe server to get things going again.  No idea if this is a sane thing \nto do, but at least my clients will pull again.\n\n`git fsck` gives me dangling blob files:\n\ndangling blob 9b08c9937daee703d97aa487d258f93ab92eb691\ndangling blob 7361898075e647e47c8835320e5481e94d8ef275\ndangling blob 359e9687e64d8f7a9fd039131fd733a9726a1bad\ndangling blob a64f34e998ae9db80ef8ea33cb30e2486829d308\ndangling blob a913d295a26ccda2fac7fc051f2e23400f187035\ndangling blob e6773de701ef3b7a9e8c80e2319dcd4629702220\n\nIt seems gc is causes corruption.\n\n\n/Allan\n"}]}