{"thread":{"id":"47243","subject":"Re: Why gc --auto is called so rarely?","startedAt":"2017-11-19T18:04:31Z","lastAt":"2017-11-20T00:46:41Z","messageCount":3,"participants":["Ilya Kantor","Eric Sunshine","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"332864","messageId":"C47F730C-18AE-411E-AC57-2DA8625451C4@icloud.com","threadId":"47243","inReplyTo":null,"subject":"Re: Why gc --auto is called so rarely?","fromName":"Ilya Kantor","fromEmail":"ilya.a.kantor@icloud.com","sentAt":"2017-11-19T17:04:21Z","receivedAt":"2017-11-19T18:04:31Z","isPatch":false,"sender":{"key":"ilya.a.kantor@icloud.com","avatar":null},"body":"...It seems sane to git gc --auto from command that are expected to take time.\n\nThat's probably the reason why it's not called on commits and called on receive-pack. \n\nBut then why call it on merges? Especially on those that have no conflicts and should run fast.\nAlso, merges are not supposed to introduce unreachable objects.\n\nP.S. The old gmane discussion referenced by some previous posts on this subject is lost.\n\n"},{"id":"332867","messageId":"CAPig+cRxB5xiyeCWKTB3O1zeH50pobjBH8oyQt75FkC09_4_dw@mail.gmail.com","threadId":"47243","inReplyTo":"C47F730C-18AE-411E-AC57-2DA8625451C4@icloud.com","subject":"Re: Why gc --auto is called so rarely?","fromName":"Eric Sunshine","fromEmail":"sunshine@sunshineco.com","sentAt":"2017-11-19T18:12:00Z","receivedAt":"2017-11-19T18:12:06Z","isPatch":false,"sender":{"key":"sunshine@sunshineco.com","avatar":"https://avatars.githubusercontent.com/u/163641?v=4"},"body":"On Sun, Nov 19, 2017 at 12:04 PM, Ilya Kantor <ilya.a.kantor@icloud.com> wrote:\n> P.S. The old gmane discussion referenced by some previous posts on this subject is lost.\n\nYou can find old gmane conversations at https://public-inbox.org/git/\nby searching for \"gmane:<id>\" in the search field, where <id> is the\ngmane ID number of the message.\n"},{"id":"332885","messageId":"xmqqa7zhojyv.fsf@gitster.mtv.corp.google.com","threadId":"47243","inReplyTo":"C47F730C-18AE-411E-AC57-2DA8625451C4@icloud.com","subject":"Re: Why gc --auto is called so rarely?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2017-11-20T00:46:32Z","receivedAt":"2017-11-20T00:46:41Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Ilya Kantor <ilya.a.kantor@icloud.com> writes:\n\n> ...It seems sane to git gc --auto from command that are expected to take time.\n>\n> That's probably the reason why it's not called on commits and\n> called on receive-pack.\n>\n> But then why call it on merges? Especially on those that have no\n> conflicts and should run fast.  Also, merges are not supposed to\n> introduce unreachable objects.\n\nThe primary thing we want the users get out of running \"gc --auto\"\nduring these operations are not the removal of unreachable garbage.\nIt is primarily run to reduce the number of loose objects and\nprevent great many numbers of tiny packfiles from being accumulated,\nso the places you see calls to it tend to be after creating new\nobjects in the repository.\n\n\n"}]}