Sidenote: correlating the single and double cases in the code with the documentation, I imagine “removed files” actually means “code from some other modified file in the same commit”, and similarly “existing files” means “code from any files in the parent commit”. * -C -C -C enables copy from existing files for * -C -C enables copy from existing files, but only The best hint is in builtin-blame.c, which says, within a function called blame_copy_callback: /* (In the GUI this is done by choosing full copy detection from the right click menu). The documentation does not seem to be very clear about the effect of three -C options on git blame. If you want to override it, use the GUI (Edit->Options), or directly set the gui.copyblamethreshold config variable. Git gui blame defaults to 40 for this – it actually sets -C40 and calls (I assume) the command line blame tool. You can override it by appending a number to the -C option. This threshold defaults to 40 characters for copy detection, and 20 for move detection. There is a concept of a “threshold”, which is the minimum number of alphanumeric characters required to count something as a code move/copy – be sure to read under -C in man git-blame. (In addition, it also appears to set -w, to ignore whitespace changes while blaming). Git gui blame behaves like -C -C by default, but can behave like -C if gui.fastcopyblame is true. When you give the flag twice, it looks for new code among all the files in the parent commit, and so it detects code that was copied. That is, it searches for new code among other files that were also modified in the same commit. When the -C flag is given only once, it looks for code blocks that were moved. It’s a very powerful feature, accessed by specifying the -C flag one or more times, but there are some nuances. As a result, the git blame and the git gui blame commands can detect code moved or copied from elsewhere in the project. If this variable is set to false, the output of these commands will be done using completely buffered I/O. Gitolite documentation has another /gitolite in the URL, so If this Boolean environment variable is set to true, then commands such as git blame (in incremental mode), git rev-list, git log, git check-attr and git check-ignore will force a flush of the output stream after each record have been flushed. '' and so ALL my git related stuff gets carried over. That's just an artifact of '' being translated to Although this page has a '' URL, this is not about gitolite.

Git blame file