| blob | 91b34abc8a8c049eb786b9c5b4b7ba740adfe377 |
4 <head>
9 /* Debug borders */
11 /*
12 border: 1px solid red;
13 */
14 }
16 body {
18 }
20 a {
23 }
26 }
28 em {
31 }
33 strong {
36 }
38 tt {
40 }
48 }
52 }
53 h2 {
55 }
56 h3 {
58 }
59 h3 + * {
61 }
66 }
68 hr {
70 }
72 p {
75 }
79 }
81 pre {
84 }
86 span#author {
91 }
92 span#email {
93 }
96 }
98 div#footer {
104 }
105 div#footer-text {
108 }
109 div#footer-badges {
112 }
114 div#preamble {
117 }
123 }
127 }
131 }
133 /* Block element titles. */
141 }
144 }
148 }
151 }
154 }
160 }
166 }
171 }
175 }
180 }
183 }
187 }
188 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
191 }
200 }
204 }
209 }
215 dl {
218 }
219 dt {
224 }
227 }
231 }
234 }
237 }
240 }
243 }
246 }
253 }
257 }
258 thead {
261 }
262 tfoot {
264 }
267 }
270 }
271 /* Because the table frame attribute is overriden by CSS in most browsers. */
274 }
278 }
282 }
288 }
291 }
294 }
300 }
303 }
307 }
311 }
315 }
317 div#toctitle {
324 }
329 }
333 }
337 }
341 }
342 /* Overrides for manpage documents */
343 h1 {
348 }
349 h2 {
351 }
354 }
358 }
360 /* Workarounds for IE6's broken and incomplete CSS2. */
366 }
373 }
379 }
384 }
388 }
392 }
397 }
399 /* IE6 sets dynamically generated links as visited. */
401 </style>
402 </head>
403 <body>
405 <h1>
406 git-blame(1) Manual Page
407 </h1>
410 <p>git-blame -
411 Show what revision and author last modified each line of a file
412 </p>
413 </div>
414 </div>
418 <div class="verseblock-content"><em>git blame</em> [-c] [-b] [-l] [--root] [-t] [-f] [-n] [-s] [-e] [-p] [-w] [--incremental] [-L n,m]
422 </div></div>
423 </div>
426 <div class="paragraph"><p>Annotates each line in the given file with information from the revision which
427 last modified the line. Optionally, start annotating from the given revision.</p></div>
429 <div class="paragraph"><p>The report does not tell you anything about lines which have been deleted or
431 interface briefly mentioned in the following paragraph.</p></div>
432 <div class="paragraph"><p>Apart from supporting file annotation, git also supports searching the
433 development history for when a code snippet occurred in a change. This makes it
434 possible to track when a code snippet was added to a file, moved or copied
435 between files, and eventually deleted or replaced. It works by searching for
436 a text string in the diff. A small example:</p></div>
439 <pre><tt>$ git log --pretty=oneline -S'blame_usage'
441 ea4c7f9bf69e781dd0cd88d2bccb2bf5cc15c9a7 git-blame: Make the output</tt></pre>
442 </div></div>
443 </div>
448 -b
449 </dt>
450 <dd>
451 <p>
452 Show blank SHA-1 for boundary commits. This can also
454 </p>
455 </dd>
457 --root
458 </dt>
459 <dd>
460 <p>
461 Do not treat root commits as boundaries. This can also be
463 </p>
464 </dd>
466 --show-stats
467 </dt>
468 <dd>
469 <p>
470 Include additional statistics at the end of blame output.
471 </p>
472 </dd>
475 </dt>
476 <dd>
477 <p>
479 one of these forms:
480 </p>
482 <li>
483 <p>
484 number
485 </p>
488 </li>
489 <li>
490 <p>
491 /regex/
492 </p>
496 </li>
497 <li>
498 <p>
499 +offset or -offset
500 </p>
503 </li>
504 </ul></div>
505 </dd>
507 -l
508 </dt>
509 <dd>
510 <p>
511 Show long rev (Default: off).
512 </p>
513 </dd>
515 -t
516 </dt>
517 <dd>
518 <p>
519 Show raw timestamp (Default: off).
520 </p>
521 </dd>
524 </dt>
525 <dd>
526 <p>
527 Use revisions from revs-file instead of calling <a href="git-rev-list.html">git-rev-list(1)</a>.
528 </p>
529 </dd>
531 --reverse
532 </dt>
533 <dd>
534 <p>
535 Walk history forward instead of backward. Instead of showing
536 the revision in which a line appeared, this shows the last
537 revision in which a line has existed. This requires a range of
538 revision like START..END where the path to blame exists in
539 START.
540 </p>
541 </dd>
543 -p
544 </dt>
546 --porcelain
547 </dt>
548 <dd>
549 <p>
550 Show in a format designed for machine consumption.
551 </p>
552 </dd>
554 --line-porcelain
555 </dt>
556 <dd>
557 <p>
558 Show the porcelain format, but output commit information for
559 each line, not just the first time a commit is referenced.
560 Implies --porcelain.
561 </p>
562 </dd>
564 --incremental
565 </dt>
566 <dd>
567 <p>
568 Show the result incrementally in a format designed for
569 machine consumption.
570 </p>
571 </dd>
574 </dt>
575 <dd>
576 <p>
577 Specifies the encoding used to output author names
579 output unconverted data. For more information see the
581 manual page.
582 </p>
583 </dd>
586 </dt>
587 <dd>
588 <p>
590 changes starting backwards from the working tree copy.
591 This flag makes the command pretend as if the working
592 tree copy has the contents of the named file (specify
594 </p>
595 </dd>
598 </dt>
599 <dd>
600 <p>
601 The value is one of the following alternatives:
602 {relative,local,default,iso,rfc,short}. If --date is not
603 provided, the value of the blame.date config variable is
604 used. If the blame.date config variable is also not set, the
605 iso format is used. For more information, See the discussion
607 </p>
608 </dd>
611 </dt>
612 <dd>
613 <p>
614 Detect moved or copied lines within a file. When a commit
615 moves or copies a block of lines (e.g. the original file
616 has A and then B, and the commit changes it to B and then
618 the movement and typically blames the lines that were moved
619 up (i.e. B) to the parent and assigns blame to the lines that
620 were moved down (i.e. A) to the child commit. With this
621 option, both groups of lines are blamed on the parent by
622 running extra passes of inspection.
623 </p>
625 alphanumeric characters that git must detect as moving/copying
626 within a file for it to associate those lines with the parent
628 </dd>
631 </dt>
632 <dd>
633 <p>
635 files that were modified in the same commit. This is
636 useful when you reorganize your program and move code
637 around across files. When this option is given twice,
638 the command additionally looks for copies from other
639 files in the commit that creates the file. When this
640 option is given three times, the command additionally
641 looks for copies from other files in any commit.
642 </p>
644 alphanumeric characters that git must detect as moving/copying
645 between files for it to associate those lines with the parent
646 commit. And the default value is 40. If there are more than one
648 take effect.</p></div>
649 </dd>
651 -h
652 </dt>
654 --help
655 </dt>
656 <dd>
657 <p>
658 Show help message.
659 </p>
660 </dd>
662 -c
663 </dt>
664 <dd>
665 <p>
667 </p>
668 </dd>
670 --score-debug
671 </dt>
672 <dd>
673 <p>
674 Include debugging information related to the movement of
677 This is the number of alphanumeric characters detected
678 as having been moved between or within files. This must be above
680 of code to have been moved.
681 </p>
682 </dd>
684 -f
685 </dt>
687 --show-name
688 </dt>
689 <dd>
690 <p>
691 Show the filename in the original commit. By default
692 the filename is shown if there is any line that came from a
693 file with a different name, due to rename detection.
694 </p>
695 </dd>
697 -n
698 </dt>
700 --show-number
701 </dt>
702 <dd>
703 <p>
704 Show the line number in the original commit (Default: off).
705 </p>
706 </dd>
708 -s
709 </dt>
710 <dd>
711 <p>
712 Suppress the author name and timestamp from the output.
713 </p>
714 </dd>
716 -e
717 </dt>
719 --show-email
720 </dt>
721 <dd>
722 <p>
723 Show the author email instead of author name (Default: off).
724 </p>
725 </dd>
727 -w
728 </dt>
729 <dd>
730 <p>
731 Ignore whitespace when comparing the parent’s version and
732 the child’s to find where the lines came from.
733 </p>
734 </dd>
737 </dt>
738 <dd>
739 <p>
742 is used for a caret to mark the boundary commit.
743 </p>
744 </dd>
745 </dl></div>
746 </div>
750 header at the minimum has the first line which has:</p></div>
752 <li>
753 <p>
755 </p>
756 </li>
757 <li>
758 <p>
759 the line number of the line in the original file;
760 </p>
761 </li>
762 <li>
763 <p>
764 the line number of the line in the final file;
765 </p>
766 </li>
767 <li>
768 <p>
769 on a line that starts a group of lines from a different
770 commit than the previous one, the number of lines in this
771 group. On subsequent lines this field is absent.
772 </p>
773 </li>
774 </ul></div>
776 at least once for each commit:</p></div>
778 <li>
779 <p>
782 for committer.
783 </p>
784 </li>
785 <li>
786 <p>
787 the filename in the commit that the line is attributed to.
788 </p>
789 </li>
790 <li>
791 <p>
792 the first line of the commit log message ("summary").
793 </p>
794 </li>
795 </ul></div>
797 header, prefixed by a TAB. This is to allow adding more
798 header elements later.</p></div>
800 already been seen. For example, two lines that are blamed to the same
801 commit will both be shown, but the details for that commit will be shown
802 only once. This is more efficient, but may require more state be kept by
804 commit information for each line, allowing simpler (but less efficient)
805 usage like:</p></div>
808 <pre><tt># count the number of lines attributed to each author
809 git blame --line-porcelain file |
810 sed -n 's/^author //p' |
811 sort | uniq -c | sort -rn</tt></pre>
812 </div></div>
813 </div>
816 <div class="paragraph"><p>Unlike <em>git blame</em> and <em>git annotate</em> in older versions of git, the extent
817 of the annotation can be limited to both line ranges and revision
818 ranges. When you are interested in finding the origin for
826 </div></div>
827 <div class="paragraph"><p>Also you can use a regular expression to specify the line range:</p></div>
831 </div></div>
832 <div class="paragraph"><p>which limits the annotation to the body of the <tt>hello</tt> subroutine.</p></div>
840 </div></div>
842 lines that have not changed since the range boundary (either the
844 weeks old in the above example) are blamed for that range
845 boundary commit.</p></div>
847 created by copy-and-paste from existing files. Sometimes this
848 indicates that the developer was being sloppy and did not
849 refactor the code properly. You can first find the commit that
850 introduced the file with:</p></div>
854 </div></div>
860 </div></div>
861 </div>
864 <div class="paragraph"><p>When called with <tt>--incremental</tt> option, the command outputs the
865 result as it is built. The output generally will talk about
866 lines touched by more recent commits first (i.e. the lines will
867 be annotated out of order) and is meant to be used by
868 interactive viewers.</p></div>
870 does not contain the actual lines from the file that is being
871 annotated.</p></div>
873 <li>
874 <p>
875 Each blame entry always starts with a line of:
876 </p>
879 <pre><tt><40-byte hex sha1> <sourceline> <resultline> <num_lines></tt></pre>
880 </div></div>
882 </li>
883 <li>
884 <p>
885 The first time that a commit shows up in the stream, it has various
886 other information about it printed out with a one-word tag at the
887 beginning of each line describing the extra commit information (author,
888 email, committer, dates, summary, etc.).
889 </p>
890 </li>
891 <li>
892 <p>
893 Unlike the Porcelain format, the filename information is always
894 given and terminates the entry:
895 </p>
899 </div></div>
900 <div class="paragraph"><p>and thus it is really quite easy to parse for some line- and word-oriented
901 parser (which should be quite natural for most scripting languages).</p></div>
903 <table><tr>
906 </td>
909 where you do not recognize the tag words (or care about that particular
910 one) at the beginning of the "extended information" lines. That way, if
911 there is ever added information (like the commit encoding or extended
912 commit commentary), a blame viewer will not care.</td>
913 </tr></table>
914 </div>
915 </li>
916 </ol></div>
917 </div>
920 <div class="paragraph"><p>If the file <tt>.mailmap</tt> exists at the toplevel of the repository, or at
921 the location pointed to by the mailmap.file configuration option, it
922 is used to map author and committer names and email addresses to
923 canonical real names and email addresses.</p></div>
925 real name of an author, whitespace, and an email address used in the
930 </div></div>
935 </div></div>
936 <div class="paragraph"><p>which allows mailmap to replace only the email part of a commit, and:</p></div>
940 </div></div>
942 commit matching the specified commit email address, and:</p></div>
946 </div></div>
948 commit matching both the specified commit name and email address.</p></div>
950 and Joe, whose names appear in the repository under several forms:</p></div>
958 </div></div>
961 would look like:</p></div>
966 </div></div>
967 <div class="paragraph"><p>Note how there is no need for an entry for <<a href="mailto:jane@laptop">jane@laptop</a>.(none)>, because the
968 real name of that author is already correct.</p></div>
970 authors:</p></div>
979 </div></div>
980 <div class="paragraph"><p>Then you might want a <tt>.mailmap</tt> file that looks like:</p></div>
988 </div></div>
989 <div class="paragraph"><p>Use hash <em>#</em> for comments that are either on their own line, or after
990 the email address.</p></div>
991 </div>
995 </div>
999 </div>
1003 </div>
1004 </div>
1005 </body>
1006 </html>