{"thread":{"id":"37132","subject":"Big repository cannot be reduced","startedAt":"2014-07-15T16:43:43Z","lastAt":"2014-07-16T15:52:10Z","messageCount":2,"participants":["Woody Wu","Michael Haggerty"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"246066","messageId":"a45d5548-b577-4588-92db-75339498034d@email.android.com","threadId":"37132","inReplyTo":null,"subject":"Big repository cannot be reduced","fromName":"Woody Wu","fromEmail":"woody.wu@vip.163.com","sentAt":"2014-07-15T16:43:43Z","receivedAt":"2014-07-15T16:43:43Z","isPatch":false,"sender":{"key":"woody.wu@vip.163.com","avatar":null},"body":"Hi,\n\nI have tried some methods introduced in the network, but always failed.  Some big files committed by me to a very old branch then the files deleted and new branches were continuously created. Now the checkout directory has grown to about 80 megabytes.  What's the right way to permenently erase those garbage big files?\n\nThanks in advance.\n-\nWoody Wu from mobile phone\n"},{"id":"246162","messageId":"53C69FAA.10306@alum.mit.edu","threadId":"37132","inReplyTo":"a45d5548-b577-4588-92db-75339498034d@email.android.com","subject":"Re: Big repository cannot be reduced","fromName":"Michael Haggerty","fromEmail":"mhagger@alum.mit.edu","sentAt":"2014-07-16T15:52:10Z","receivedAt":"2014-07-16T15:52:10Z","isPatch":false,"sender":{"key":"mhagger@alum.mit.edu","avatar":"https://avatars.githubusercontent.com/u/119718?v=4"},"body":"On 07/15/2014 09:43 AM, Woody Wu wrote:\n> I have tried some methods introduced in the network, but always\n> failed.  Some big files committed by me to a very old branch then the\n> files deleted and new branches were continuously created. Now the\n> checkout directory has grown to about 80 megabytes.  What's the right\n> way to permenently erase those garbage big files?\n\nYou probably need to use \"git filter-branch\" or maybe BFG\n(http://rtyley.github.io/bfg-repo-cleaner/) to rewrite history as if the\nbig files had never been committed.  But beware of the warnings about\nrewriting history--for example, any collaborators will have to rebase\ntheir branches onto the new history.\n\nMichael\n\n-- \nMichael Haggerty\nmhagger@alum.mit.edu\n"}]}