Re: Following renames

From
Marco Costalba <hidden>
Date
2016-06-15 22:42:22
Reply to
Linus Torvalds, 2016-06-15
On 3/27/06, Linus Torvalds [off-list ref] wrote:

On Sun, 26 Mar 2006, Marco Costalba wrote:
quoted
FIRST WAY

After annotating a file history (double click on a file name in
bottom-right window or directly from tree view), you see the whole
file annotated. If you have the diff window open you see also the
corresponding patch (scrolled to selected file name).
The problem is that this step is already _way_ too expensive.

I don't want to work with any tool that makes "Step 1" take a minute or
two for a project that has a few years of history. Try it on the linux
historic project with some file that gets lots of modifications.
Historic Linux test (63428 revisions)

File: drivers/net/tg3.c
Revisions that modify tg3.c : 292

With qgit
15s to retrieve file history (git-rev-list)
19.5s to annotate (git-diff-tree -p, current GNU algorithm, not new faster one)

and...

$ time git-whatchanged HEAD drivers/net/tg3.c > /dev/null
98.01user 2.44system 1:46.19elapsed 94%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (797major+43033minor)pagefaults 0swaps

NOTE: It seems that  git-whatchanged asks for checked the out file to
work. It didn't work with no repository checked out.


Marco
Thread (24 messages) 24 messages, 10 authors, 2016-06-15
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help