Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 2.3.0 → 2.3.5 no changes
- 2.2.2 01/12/15
- 2.2.1 12/17/14
- 2.2.0 11/26/14
- 2.1.4 12/17/14
- 2.1.2 → 2.1.3 no changes
- 2.1.1 09/19/14
- 2.0.1 → 2.1.0 no changes
- 2.0.0 05/28/14
- 1.9.5 12/17/14
- 184.108.40.206 → 1.9.4 no changes
- 220.127.116.11 02/05/14
- 18.104.22.168 01/13/14
- 22.214.171.124 → 126.96.36.199 no changes
- 1.8.5 11/27/13
- 188.8.131.52 → 184.108.40.206 no changes
- 1.8.4 08/23/13
- 220.127.116.11 → 18.104.22.168 no changes
- 1.8.2 03/13/13
- 22.214.171.124 → 126.96.36.199 no changes
- 1.7.8 12/02/11
git-annotate(1) Manual Page
git-annotate - Annotate file lines with commit info
git annotate [options] file [revision]
Annotates each line in the given file with information from the commit which introduced the line. Optionally annotate from a given revision.
The only difference between this command and git-blame(1) is that they use slightly different output formats, and this command exists only for backward compatibility to support existing scripts, and provide more familiar command name for people coming from other SCM systems.
Show blank SHA-1 for boundary commits. This can also be controlled via the blame.blankboundary config option.
Do not treat root commits as boundaries. This can also be controlled via the blame.showroot config option.
Include additional statistics at the end of blame output.
- -L <start>,<end>
Annotate only the given line range. <start> and <end> can take one of these forms:
If <start> or <end> is a number, it specifies an absolute line number (lines count from 1).
This form will use the first line matching the given POSIX regex. If <end> is a regex, it will search starting at the line given by <start>.
+offset or -offset
This is only valid for <end> and will specify a number of lines before or after the line given by <start>.
Show long rev (Default: off).
Show raw timestamp (Default: off).
- -S <revs-file>
Use revs from revs-file instead of calling git-rev-list(1).
Walk history forward instead of backward. Instead of showing the revision in which a line appeared, this shows the last revision in which a line has existed. This requires a range of revision like START..END where the path to blame exists in START.
Show in a format designed for machine consumption.
Show the result incrementally in a format designed for machine consumption.
Specifies the encoding used to output author names and commit summaries. Setting it to none makes blame output unconverted data. For more information see the discussion about encoding in the git-log(1) manual page.
- --contents <file>
When <rev> is not specified, the command annotates the changes starting backwards from the working tree copy. This flag makes the command pretend as if the working tree copy has the contents of the named file (specify - to make the command read from the standard input).
Detect moving lines in the file as well. When a commit moves a block of lines in a file (e.g. the original file has A and then B, and the commit changes it to B and then A), traditional blame algorithm typically blames the lines that were moved up (i.e. B) to the parent and assigns blame to the lines that were moved down (i.e. A) to the child commit. With this option, both groups of lines are blamed on the parent.
<num> is optional but it is the lower bound on the number of alphanumeric characters that git must detect as moving within a file for it to associate those lines with the parent commit.
In addition to -M, detect lines copied from other files that were modified in the same commit. This is useful when you reorganize your program and move code around across files. When this option is given twice, the command looks for copies from all other files in the parent for the commit that creates the file in addition.
<num> is optional but it is the lower bound on the number of alphanumeric characters that git must detect as moving between files for it to associate those lines with the parent commit.
Show help message.
Written by Ryan Anderson <firstname.lastname@example.org>.
Part of the git(1) suite