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

Git has bad performance when traversing change-sets with large PPM files

From
LWLaine Walker-Avina <lwalkera@pasco.com>
Date
Feb 19, 2010, 21:24 UTC
Message-ID
<dfb660301002191324i7aeca7f5x990501bbca1475a9@mail.gmail.com>
Steps to reproduce:
1. Create a new git repo and add a 640x480 PPM image in ASCII format
2. Add a .gitattributes file with the line "*.ppm binary"
3. Commit the PPM file
4. Change the PPM image's contents
5. Add and commit
6. Try to do a git rebase -i to the initial commit
7. Watch the CPU peg at 100%
I'm using git version 1.6.3.3
Please CC me, I'm not on the list.
Thanks,
-- 
Laine Walker-Avina
Firmware Engineer
PASCO scientific
Next: Thomas Rast
Message 1 of 8 in “Git has bad performance when traversing change-sets with large PPM files”
  1. Laine Walker-AvinaFeb 19, 2010
  2. rebase -i: avoid --cherry-pick when rebasing to a direct ancestorThomas Rast, Feb 19, 2010
  3. Thomas RastFeb 20, 2010
  4. Jeff KingFeb 20, 2010
  5. cherry_pick_list: quit early if one side is emptyThomas Rast, Feb 20, 2010
  6. Jeff KingFeb 21, 2010
  7. Thomas RastFeb 20, 2010
  8. Jeff KingFeb 21, 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.