"=20
Okay, let's try to assume for now that nobody said "git blame". Instead =
let's say:
git rev-list and git log (with or without -p) perform poorly when invoked=
with a pathspec.
it=20
t=20
=20
I agreee with those numbers. However, on a converted KDE repo, they are =
*completely* different:
git log kdelibs/README takes 1:18. One minute, eighteen seconds.
git rev-list and git blame take roughly the same time.
This particular file has 64 revisions. However there are ~ 375000 revisi=
ons in the converted repo.
My and also Shawn's point was not about the speed of git blame itself. I=
t is about pathspec/rev operations. The operation time does not scale wi=
th the number of changes to the file/object/call-it-whatever, but with th=
e number of total commits in the branch.
That's what we were getting at. Not the superiority of git blame (no iro=
ny) and thus reduced speed, but the algorithmic deficiency of any operati=
on on a pathspec/object, which can be easily fixed.
cheers
simon
--=20
Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\
Work - Mac +++ space for low =E2=82=AC=E2=82=AC=E2=82=AC NOW!1 +++=
Campaign \ /
Party Enjoy Relax | http://dragonflybsd.org Against HTML \
Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \