Documentation/blame-options.txt

   1 -b::
   2         Show blank SHA-1 for boundary commits.  This can also
   3         be controlled via the `blame.blankboundary` config option.
   4
   5 --root::
   6         Do not treat root commits as boundaries.  This can also be
   7         controlled via the `blame.showroot` config option.
   8
   9 --show-stats::
  10         Include additional statistics at the end of blame output.
  11
  12 -L <start>,<end>::
  13         Annotate only the given line range.  <start> and <end> can take
  14         one of these forms:
  15
  16         - number
  17 +
  18 If <start> or <end> is a number, it specifies an
  19 absolute line number (lines count from 1).
  20 +
  21
  22 - /regex/
  23 +
  24 This form will use the first line matching the given
  25 POSIX regex.  If <end> is a regex, it will search
  26 starting at the line given by <start>.
  27 +
  28
  29 - +offset or -offset
  30 +
  31 This is only valid for <end> and will specify a number
  32 of lines before or after the line given by <start>.
  33 +
  34
  35 -l::
  36         Show long rev (Default: off).
  37
  38 -t::
  39         Show raw timestamp (Default: off).
  40
  41 -S <revs-file>::
  42         Use revs from revs-file instead of calling linkgit:git-rev-list[1].
  43
  44 -p::
  45 --porcelain::
  46         Show in a format designed for machine consumption.
  47
  48 --incremental::
  49         Show the result incrementally in a format designed for
  50         machine consumption.
  51
  52 --contents <file>::
  53         When <rev> is not specified, the command annotates the
  54         changes starting backwards from the working tree copy.
  55         This flag makes the command pretend as if the working
  56         tree copy has the contents of the named file (specify
  57         `-` to make the command read from the standard input).
  58
  59 -M|<num>|::
  60         Detect moving lines in the file as well.  When a commit
  61         moves a block of lines in a file (e.g. the original file
  62         has A and then B, and the commit changes it to B and
  63         then A), traditional 'blame' algorithm typically blames
  64         the lines that were moved up (i.e. B) to the parent and
  65         assigns blame to the lines that were moved down (i.e. A)
  66         to the child commit.  With this option, both groups of lines
  67         are blamed on the parent.
  68 +
  69 <num> is optional but it is the lower bound on the number of
  70 alphanumeric characters that git must detect as moving
  71 within a file for it to associate those lines with the parent
  72 commit.
  73
  74 -C|<num>|::
  75         In addition to `-M`, detect lines copied from other
  76         files that were modified in the same commit.  This is
  77         useful when you reorganize your program and move code
  78         around across files.  When this option is given twice,
  79         the command looks for copies from all other files in the
  80         parent for the commit that creates the file in addition.
  81 +
  82 <num> is optional but it is the lower bound on the number of
  83 alphanumeric characters that git must detect as moving
  84 between files for it to associate those lines with the parent
  85 commit.
  86
  87 -h::
  88 --help::
  89         Show help message.