我最近一直在使用Fugitive的Gblame,但不太明白“reblame”的作用.
有人可以更清楚地描述这些选项的作用：
- reblame at commit ~ reblame at [count]th first grandparent P reblame at [count]th parent (like HEAD^[count])
将reblame视为导航到提交然后对您的文件或git责备运行责备< commit> – < file>
原文链接：/bash/383632.html> – 最简单的情况.使用光标下的提交并重新启动文件.
>〜相当于运行git blame< rev>〜[count] – < file>
> P相当于运行git blame< rev> ^ [count] – < file>
对于常见情况,即没有[count],〜和P是等价的. (注意[count]默认为1)
Here is an illustration,by Jon Loeliger.
Both commit nodes B and C are parents of commit node A.
Parent commits are ordered left-to-right.
G H I J
\ / \ /
D E F
\ | / \
\ | / |
\|/ |
B C
\ /
\ /
A
A = = A^0
B = A^ = A^1 = A~1
C = A^2 = A^2
D = A^^ = A^1^1 = A~2
E = B^2 = A^^2
F = B^3 = A^^3
G = A^^^ = A^1^1^1 = A~3
H = D^2 = B^^2 = A^^^2 = A~2^2
I = F^ = B^3^ = A^^3^
J = F^2 = B^3^2 = A^^3^2
要了解有关git修订符号的更多信息,请参阅：
> git help gitrevisions
> Git Tools – Revision Selection
> Carats and Tildes,Resets and Reverts注意：本文正在讨论重置,但图形和修订部分对文章的中间部分有帮助.
有关git blame的更多帮助,请参阅git help blame
