{"thread":{"id":"47239","subject":"Why gc --auto is called so rarely?","startedAt":"2017-11-19T14:56:08Z","lastAt":"2017-11-19T14:56:08Z","messageCount":1,"participants":["Ilya Kantor"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"332850","messageId":"CAFU8umg-utVnUZadvkp-6pA7Oj+-z2pBdfUR64BnyBnprVzoyw@mail.gmail.com","threadId":"47239","inReplyTo":null,"subject":"Why gc --auto is called so rarely?","fromName":"Ilya Kantor","fromEmail":"iliakan@gmail.com","sentAt":"2017-11-19T14:55:40Z","receivedAt":"2017-11-19T14:56:08Z","isPatch":false,"sender":{"key":"iliakan@gmail.com","avatar":"https://avatars.githubusercontent.com/u/349336?v=4"},"body":"Hello,\n\nI tried to find places where git gc --auto is called, and found that\nthere's only a few.\n\nFirst, in *some* merges. That is, if there was a conflict during the\nmerge, that is resolved, then it's not called.\n\nThen in\n* receive-pack\n* fetch\n* am\n\nIs there any logic in such assignments? Why there?\n\nIn particular, gc --auto was called in commits earlier, but not in the\nrecent versions of git.\n\n---\nBest Regards,\nIlya Kantor\n"}]}