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

Re: Rewriting history with git-filter-branch and leaking objects (?)

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 17, 2007, 21:11 UTC
Message-ID
<7vzm0pg92c.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<86k5ruxdxz.fsf@lola.quinscape.zz>
David Kastrup <dak@gnu.org> writes:
Show 12 quoted lines
> Mike Hommey <mh@glandium.org> writes:
>
>> I've been playing with git-filter-branch, and was wondering how objects
>> from the original branch are supposed to be removed.
>>
>> It looks like removing the refs/original/* refs is not enough.
>>
>> And it also looks like when all references seem to be removed, git-prune
>> doesn't fully do its job...
>
> It is quite quite hard to get rid of objects.  You need to get the
> reflogs for the commits and the files expired.

An easier way is probably to make a new clone in the neighbouring directory locally.

Previous: Sam VilainNext: Mike Hommey
Message 5 of 7 in “Rewriting history with git-filter-branch and leaking objects (?)”
  1. Mike HommeyAug 17, 2007
  2. David KastrupAug 17, 2007
  3. Mike HommeyAug 17, 2007
  4. Sam VilainAug 19, 2007
  5. Junio C HamanoAug 17, 2007
  6. Mike HommeyAug 17, 2007
  7. Mike HommeyAug 19, 2007

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.