Re: Git's database structure

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: Git's database structure

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:33

Andreas Ericsson [off-list ref] writes:
Estimated daily uses of git-blame, world-wide: few
Estimated daily uses of git-{merge,diff}, worldwide: lots
Which makes the author of git-blame weep X-<.

The real issue is that embedding pathname in blob does _not_
help "git blame" but would actively hurt it.  A file with the
identical contents moved between the parent to child commit
shares the same blob object and same object name in the real
git.  Jon's modified system that hashes pathname together with
the contents would have them as two completely unrelated objects
with different object names, which only means that even 100%
similarity rename case becomes as expensive to find as renames
of lower similarity, which needs to expand and look into blob
contents.

Re: Git's database structure

From: Wincent Colaiuta <hidden>
Date: 2016-06-15 22:43:33

El 6/9/2007, a las 11:09, Junio C Hamano escribió:
Andreas Ericsson [off-list ref] writes:
quoted
Estimated daily uses of git-blame, world-wide: few
Estimated daily uses of git-{merge,diff}, worldwide: lots
Which makes the author of git-blame weep X-<.
But the few times when you do use git-blame (apart from when you use  
it out of sheer curiosity) it usually saves you backside (ie. when  
you've located a problem in the code and you want to know the who/ 
what/when/why of the offending commit).

Cheers,
Wincent
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help