1git-blame(1) 2============ 3 4NAME 5---- 6git-blame - Show what revision and author last modified each line of a file 7 8SYNOPSIS 9-------- 10'git-blame' [-c] [-l] [-t] [-S <revs-file>] [--] <file> [<rev>] 11 12DESCRIPTION 13----------- 14 15Annotates each line in the given file with information from the revision which 16last modified the line. Optionally, start annotating from the given revision. 17 18This report doesn't tell you anything about lines which have been deleted or 19replaced; you need to use a tool such as gitlink:git-diff[1] or the "pickaxe" 20interface briefly mentioned in the following paragraph. 21 22Apart from supporting file annotation, git also supports searching the 23development history for when a code snippet occured in a change. This makes it 24possible to track when a code snippet was added to a file, moved or copied 25between files, and eventually deleted or replaced. It works by searching for 26a text string in the diff. A small example: 27 28----------------------------------------------------------------------------- 29$ git log --pretty=oneline -S'blame_usage' 305040f17eba15504bad66b14a645bddd9b015ebb7 blame -S <ancestry-file> 31ea4c7f9bf69e781dd0cd88d2bccb2bf5cc15c9a7 git-blame: Make the output 32----------------------------------------------------------------------------- 33 34OPTIONS 35------- 36-c, --compatibility:: 37 Use the same output mode as gitlink:git-annotate[1] (Default: off). 38 39-l, --long:: 40 Show long rev (Default: off). 41 42-t, --time:: 43 Show raw timestamp (Default: off). 44 45-S, --rev-file <revs-file>:: 46 Use revs from revs-file instead of calling gitlink:git-rev-list[1]. 47 48-h, --help:: 49 Show help message. 50 51 52SEE ALSO 53-------- 54gitlink:git-annotate[1] 55 56AUTHOR 57------ 58Written by Fredrik Kuivinen <freku045@student.liu.se>. 59 60GIT 61--- 62Part of the gitlink:git[7] suite