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

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

From
Mike Hommey <mh@glandium.org>
Date
Aug 19, 2007, 19:59 UTC
Message-ID
<20070819195900.GA1313@glandium.org>
In-Reply-To
<20070817183115.GA15653@glandium.org>
On Fri, Aug 17, 2007 at 08:31:15PM +0200, Mike Hommey <mh@glandium.org> wrote:
Show 7 quoted lines
> On Fri, Aug 17, 2007 at 07:18:51PM +0200, Mike Hommey <mh@glandium.org> wrote:
> > $ rm .git/logs/refs/heads/master 
> > $ rm .git/logs/HEAD
> 
> git-reflog expire --expire-unreachable=$(date +%s) --all
> 
> is cleaner, but git prune -n still misses a tree.

FWIW, I found out what was happening, and why there was still a tree not being pruned: it was used by the index.

So all in all, no spurious object after cleanup.
Mike
Previous: Mike Hommey
Message 7 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.