Thread (44 messages) flat view 44 messages, 12 authors, 2016-06-15

Re: More precise tag following

From: Jakub Narebski <hidden>
Date: 2016-06-15 22:42:51

Linus Torvalds wrote:
On Sat, 27 Jan 2007, Linus Torvalds wrote:
quoted
Quoth Simon 'corecode' Schubert:
quoted
quoted
git log kdelibs/README takes 1:18.  One minute, eighteen seconds.
git rev-list and git blame take roughly the same time.
Btw, why do people even think this is "slow"?

Yeah, we should speed it up, just because I think having that large a repo 
will make it more obvious what we can do even better. No question about 
that.
[...]
Basically, asking for "git log --since=1.week.ago" should be 
constant-time, regardless of how big the history is (well, it obviously 
depends on how many changes there have been in the last week, but the 
point is that it shouldn't get slower over time).
[...]
That's why "git blame" is so horrible. It's fundamentally an operation 
that depends on "whole history" and thus cannot scale.
By the way, in git-blame you can also give the cutoff like in git-log;
the lines which come from outside given revision range either get blamed
on boundary, or are shown "unblamed".

I wonder if any other SCM's blame/annotate has that...
-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help