1. In git-gui blame viewer you can click on shortened sha1 of a commit
to see file at given version. Unfortunately git-gui goes to other
version of a file by reblaming a file starting from scratch.
It would be nice to have
git blame --incremental=<revision1> <revision2> -- <file>
which would blame only lines which differ between <revision1>
and <revision2>. We can assume that <revision2> is ancestor of
<revision1>, I think. I'm not completely sure if it is possible
and reasonable, i.e. if one can assume that only lines which
differ need reblaming...
And of course use this feature in "git-gui blame" which should
speed up exploring file history a bit.
2. Sometimes I'm interested only in part of a file. Thus I'd like
"git-gui blame" to understand line-range parameter of git-blame.
It means that I'd like to be able to say for example:
git gui blame -L '/^sub git_feed/,/^}$/' HEAD -- gitweb/gitweb.perl
and have only given range of lines blamed, with the rest grayed out
in the "inactive control" style. Of course in the case I specified
line range incorrectly, I'd like to have menu entry or a button to
reblame _whole_ file... Or perhaps do blaming of a whole file in the
background, after blaming specified range fo lines.
This should speed up "git gui blame" a bit. By the way, of course
git-gui should start with the selected line-range visible.
3. Sometimes when reviewing patches I do wonder: why the preimage looks
like it looks like. It would be useful in that situation to be able
to blame the patch (context lines and pre-image lines). Although I'm
not suer if it would bevery useful and used often [enough].
P.S. qgit uses some bottom-up all-files mechanism to get the blame of
all the files together. Could anyone describe in few sentences the
algorithm qgit uses? Would it be useful to put it available e.g. in
gitlib-thin for other viewers, or not; what do you think?
P.P.S. Of couse the examples and ideas are not limited to "git gui
blame"...
--
Jakub Narebski
Poland
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
