![]() Show in a format designed for machine consumption. END where the path to blame exists in START. This requires a range of revision like START. Instead of showing the revision in which a line appeared, this shows the last revision in which a line hasĮxisted. Walk history forward instead of backward. Use revisions from revs-file instead of calling git-rev-list (1 ). “: ” 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 This is only valid for and will specify a number of lines before or after 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Īny, 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 ). “-L ” or “-L ,” spans from to end of file. Include additional statistics at the end of blame output.Īnnotate only the given line range. This can also be controlled via the blame.showRoot config option. This can also be controlled via the blame.blankboundary config option.ĭo not treat root commits as boundaries. A small example of the pickaxe interface that searches for blame_usage: Possible to track when a code snippet was added to a file, moved or copied between files, and eventually deleted or replaced. The report does not tell you anything about lines which have been deleted or replaced you need to use a tool such as git diff or the "pickaxe" interfaceīriefly mentioned in the following paragraph.Īpart from supporting file annotation, Git also supports searching the development history for when a code snippet occurred in a change. Moved from one file to another, or to follow lines that were copied and pasted from another file, etc., see the -C and -M options. The origin of lines is automatically followed across whole-file renames (currently there is no option to turn the rename-following off ). When specified one or more times, -L restricts annotation to the requested lines. Optionally, start annotating from the given revision. ![]() Git blame Īnnotates each line in the given file with information from the revision which last modified the line. Git-blame - Show what revision and author last modified each line of a file ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |