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

Re: Possible git bug when using filter-branch to remove large binaries

From
Thomas Rast <trast@student.ethz.ch>
Date
Feb 15, 2009, 21:55 UTC
Message-ID
<200902152255.05655.trast@student.ethz.ch>
In-Reply-To
<34854909-55F5-4869-A7A6-0E179F2F7A44@talkhouse.com>
Juan Zanos wrote:
> I'm trying to remove a directory of large binaries from a git  
> repository
[...]
> The directory successfully  
> vanishes. However, the repository + working directory only goes from  
> 216M down to 133M.   That means the binaries were only removed from  
> the working directory.

We're in fact trying to make a generic recipe and put it in 'man git-filter-branch'. The preliminary patch is here:

  http://article.gmane.org/gmane.comp.version-control.git/109925/

Once you convince your eyes to ignore the leading +, it should be fairly easy to read in patch form. ;-)

It would be very helpful if you could try the recipe, and report if it worked.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch
Previous: Juan Zanos
Message 2 of 2 in “Possible git bug when using filter-branch to remove large binaries”
  1. Juan ZanosFeb 15, 2009
  2. Thomas RastFeb 15, 2009

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.