From: Laine Walker-Avina <lwalkera@pasco.com>
To: git@vger.kernel.org
Subject: Git has bad performance when traversing change-sets with large PPM files
Date: Fri, 19 Feb 2010 13:24:05 -0800 [thread overview]
Message-ID: <dfb660301002191324i7aeca7f5x990501bbca1475a9@mail.gmail.com> (raw)
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 reply other threads:[~2010-02-19 21:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 21:24 Laine Walker-Avina [this message]
2010-02-19 23:30 ` [PATCH] rebase -i: avoid --cherry-pick when rebasing to a direct ancestor Thomas Rast
2010-02-20 0:02 ` Thomas Rast
2010-02-20 7:27 ` Jeff King
2010-02-20 11:42 ` [PATCH] cherry_pick_list: quit early if one side is empty Thomas Rast
2010-02-21 6:50 ` Jeff King
2010-02-20 13:38 ` [PATCH] rebase -i: avoid --cherry-pick when rebasing to a direct ancestor Thomas Rast
2010-02-21 7:46 ` Jeff King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dfb660301002191324i7aeca7f5x990501bbca1475a9@mail.gmail.com \
--to=lwalkera@pasco.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).