Aaron Bentley wrote:Well without the content based detection of contents copying and moving which git-blame wouldn't work as well as it work now. But you don't have content movement tracking. I think not. The first example: $ time git blame -C revision.c >/dev/null real 0m7.577s user 0m7.248s sys 0m0.020s while without content copying and moving detection we have $ time git blame revision.c >/dev/null real 0m2.108s user 0m2.044s sys 0m0.024s (on 2000 BogoMIPS CPU). -- Jakub Narebski Warsaw, Poland ShadeHawk on #git - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Arjan van de Ven | Re: Linux 2.6.27-rc8 |
git: | |
| Arjan van de Ven | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Jeff Garzik | Re: [bug?] tg3: Failed to load firmware "tigon/tg3_tso.bin" |
