git-annotate - Annotate file lines with commit information


   git annotate [options] file [revision]


   Annotates each line in the given file with information from the commit
   which introduced the line. Optionally annotates 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 a 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>, -L :<funcname>
       Annotate only the given line range. May be specified multiple
       times. Overlapping ranges are allowed.

       <start> and <end> are optional. "-L <start>" or "-L <start>," spans
       from <start> to end of file. "-L ,<end>" spans from start of file
       to <end>.

       <start> and <end> can take one of these forms:

       *   number

           If <start> or <end> is a number, it specifies an absolute line
           number (lines count from 1).

       *   /regex/

           This form will use the first line matching the given POSIX
           regex. If <start> is a regex, it will search from the end of
           the previous -L range, if any, otherwise from the start of
           file. If <start> is "^/regex/", it will search from the start
           of file. 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>.

       If ":<funcname>" is given in place of <start> and <end>, it is a
       regular expression that denotes the range from the first funcname
       line that matches <funcname>, up to the next funcname line.
       ":<funcname>" searches from the end of the previous -L range, if
       any, otherwise from the start of file. "^:<funcname>" searches from
       the start of file.

       Show long rev (Default: off).

       Show raw timestamp (Default: off).

   -S <revs-file>
       Use revisions 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.

   -p, --porcelain
       Show in a format designed for machine consumption.

       Show the porcelain format, but output commit information for each
       line, not just the first time a commit is referenced. Implies

       Show the result incrementally in a format designed for machine

       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

   --date <format>
       Specifies the format used to output dates. If --date is not
       provided, the value of the config variable is used. If
       the config variable is also not set, the iso format is
       used. For supported values, see the discussion of the --date option
       at git-log(1).

       Progress status is reported on the standard error stream by default
       when it is attached to a terminal. This flag enables progress
       reporting even if not attached to a terminal. Can't use --progress
       together with --porcelain or --incremental.

       Detect moved or copied lines within a file. When a commit moves or
       copies a block of lines (e.g. the original file has A and then B,
       and the commit changes it to B and then A), the traditional blame
       algorithm notices only half of the movement and 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 by running extra passes of inspection.

       <num> is optional but it is the lower bound on the number of
       alphanumeric characters that Git must detect as moving/copying
       within a file for it to associate those lines with the parent
       commit. The default value is 20.

       In addition to -M, detect lines moved or 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 additionally looks for
       copies from other files in the commit that creates the file. When
       this option is given three times, the command additionally looks
       for copies from other files in any commit.

       <num> is optional but it is the lower bound on the number of
       alphanumeric characters that Git must detect as moving/copying
       between files for it to associate those lines with the parent
       commit. And the default value is 40. If there are more than one -C
       options given, the <num> argument of the last -C will take effect.

       Show help message.




   Part of the git(1) suite


Personal Opportunity - Free software gives you access to billions of dollars of software at no cost. Use this software for your business, personal use or to develop a profitable skill. Access to source code provides access to a level of capabilities/information that companies protect though copyrights. Open source is a core component of the Internet and it is available to you. Leverage the billions of dollars in resources and capabilities to build a career, establish a business or change the world. The potential is endless for those who understand the opportunity.

Business Opportunity - Goldman Sachs, IBM and countless large corporations are leveraging open source to reduce costs, develop products and increase their bottom lines. Learn what these companies know about open source and how open source can give you the advantage.

Free Software

Free Software provides computer programs and capabilities at no cost but more importantly, it provides the freedom to run, edit, contribute to, and share the software. The importance of free software is a matter of access, not price. Software at no cost is a benefit but ownership rights to the software and source code is far more significant.

Free Office Software - The Libre Office suite provides top desktop productivity tools for free. This includes, a word processor, spreadsheet, presentation engine, drawing and flowcharting, database and math applications. Libre Office is available for Linux or Windows.

Free Books

The Free Books Library is a collection of thousands of the most popular public domain books in an online readable format. The collection includes great classical literature and more recent works where the U.S. copyright has expired. These books are yours to read and use without restrictions.

Source Code - Want to change a program or know how it works? Open Source provides the source code for its programs so that anyone can use, modify or learn how to write those programs themselves. Visit the GNU source code repositories to download the source.


Study at Harvard, Stanford or MIT - Open edX provides free online courses from Harvard, MIT, Columbia, UC Berkeley and other top Universities. Hundreds of courses for almost all major subjects and course levels. Open edx also offers some paid courses and selected certifications.

Linux Manual Pages - A man or manual page is a form of software documentation found on Linux/Unix operating systems. Topics covered include computer programs (including library and system calls), formal standards and conventions, and even abstract concepts.