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. When a commit moves or copies a block of lines (e.g. Mĭetect moved or copied lines within a file. Can’t use -progress together with -porcelain or -incremental. This flag enables progress reporting even if not attached to a terminal. Progress status is reported on the standard error stream by default when it is attached to a terminal. For supported values, see the discussion of the -date option at git-log.
#Git annotate iso
If the blame.date config variable is also not set, the iso format is used. If -date is not provided, the value of the blame.date config variable is used. Specifies the format used to output dates. 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). When is not specified, the command annotates the changes starting backwards from the working tree copy.
#Git annotate manual
For more information see the discussion about encoding in the git-log manual page. Setting it to none makes blame output unconverted data.
Specifies the encoding used to output author names and commit summaries. Show the result incrementally 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. Show in a format designed for machine consumption. This option can be used to determine when a line was introduced to a particular integration branch, rather than when it was introduced to the history overall. first-parentįollow only the first parent commit upon seeing a merge commit. git blame -reverse START is taken as git blame -reverse START.HEAD for convenience. This requires a range of revision like START.END where the path to blame exists in START. Instead of showing the revision in which a line appeared, this shows the last revision in which a line has existed. Walk history forward instead of backward. Use revisions from revs-file instead of calling git-rev-list.
#Git annotate Patch
The function names are determined in the same way as git diff works out patch hunk headers (see Defining a custom hunk-header in gitattributes). : searches from the end of the previous -L range, if any, otherwise from the start of file.
If : is given in place of and, it is a regular expression that denotes the range from the first funcname line that matches, up to the next funcname line. This is only valid for and will specify a number of lines before or after the line given by. If is a regex, it will search starting at the line given by. If is ^/regex/, it will search from the start of file. If is a regex, it will search from the end of the previous -L range, if any, otherwise from the start of file. This form will use the first line matching the given POSIX regex. If or is a number, it specifies an absolute line number (lines count from 1).
0 kommentar(er)
