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

Re: Extremely slow progress during 'git reflog expire --all'

From
FPFrans Pop <elendil@planet.nl>
Date
Apr 2, 2010, 21:50 UTC
Message-ID
<201004022350.20999.elendil@planet.nl>
In-Reply-To
<20100402212858.GA28531@coredump.intra.peff.net>
On Friday 02 April 2010, Jeff King wrote:
> Can you reproduce the problem on your repo? If so, can you possibly tar
> it up and make it available (probably just the .git directory would be
> enough)?

Yes, I can reproduce. I've run it a few times and broke it off each time before it finished as I really had no idea how much longer it might take.

$ du -sh .git 1008M .git

I can make that available, but it's going to take a while to upload and I don't want to leave it up too long as I'll be abusing a project service for that. So the people who want to look at it would have grab it fairly promptly (within 2 days or so).

Is that OK?

Cheers, FJP

Previous: Jeff KingNext: Jeff King
Message 3 of 15 in “Extremely slow progress during 'git reflog expire --all'”
  1. Frans PopApr 2, 2010
  2. Jeff KingApr 2, 2010
  3. Frans PopApr 2, 2010
  4. Jeff KingApr 2, 2010
  5. Frans PopApr 3, 2010
  6. Jeff KingApr 3, 2010
  7. Jeff KingApr 3, 2010
  8. Junio C HamanoApr 4, 2010
  9. Jeff KingApr 5, 2010
  10. Junio C HamanoApr 5, 2010
  11. Jeff KingApr 6, 2010
  12. Re*: Extremely slow progress during 'git reflog expire --all'Junio C Hamano, Apr 7, 2010
  13. Junio C HamanoApr 7, 2010
  14. Jeff KingApr 8, 2010
  15. Jeff KingApr 8, 2010

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.