git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Big repository cannot be reduced

From
Michael Haggerty <mhagger@alum.mit.edu>
Date
Jul 16, 2014, 15:52 UTC
Message-ID
<53C69FAA.10306@alum.mit.edu>
In-Reply-To
<a45d5548-b577-4588-92db-75339498034d@email.android.com>
On 07/15/2014 09:43 AM, Woody Wu wrote:
Show 5 quoted lines
> I 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?

You probably need to use "git filter-branch" or maybe BFG (http://rtyley.github.io/bfg-repo-cleaner/) to rewrite history as if the big files had never been committed. But beware of the warnings about rewriting history--for example, any collaborators will have to rebase their branches onto the new history.

Michael
-- 
Michael Haggerty
mhagger@alum.mit.edu
Previous: Woody Wu
Message 2 of 2 in “Big repository cannot be reduced”
  1. Woody WuJul 15, 2014
  2. Michael HaggertyJul 16, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.