| blob | c45b75ea5f019f44fedddd19b79403fac2344bc9 |
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 --incremental
555 </dt>
556 <dd>
557 <p>
558 Show the result incrementally in a format designed for
559 machine consumption.
560 </p>
561 </dd>
564 </dt>
565 <dd>
566 <p>
567 Specifies the encoding used to output author names
569 output unconverted data. For more information see the
571 manual page.
572 </p>
573 </dd>
576 </dt>
577 <dd>
578 <p>
580 changes starting backwards from the working tree copy.
581 This flag makes the command pretend as if the working
582 tree copy has the contents of the named file (specify
584 </p>
585 </dd>
588 </dt>
589 <dd>
590 <p>
591 The value is one of the following alternatives:
592 {relative,local,default,iso,rfc,short}. If --date is not
593 provided, the value of the blame.date config variable is
594 used. If the blame.date config variable is also not set, the
595 iso format is used. For more information, See the discussion
597 </p>
598 </dd>
601 </dt>
602 <dd>
603 <p>
604 Detect moved or copied lines within a file. When a commit
605 moves or copies a block of lines (e.g. the original file
606 has A and then B, and the commit changes it to B and then
608 the movement and typically blames the lines that were moved
609 up (i.e. B) to the parent and assigns blame to the lines that
610 were moved down (i.e. A) to the child commit. With this
611 option, both groups of lines are blamed on the parent by
612 running extra passes of inspection.
613 </p>
615 alphanumeric characters that git must detect as moving/copying
616 within a file for it to associate those lines with the parent
618 </dd>
621 </dt>
622 <dd>
623 <p>
625 files that were modified in the same commit. This is
626 useful when you reorganize your program and move code
627 around across files. When this option is given twice,
628 the command additionally looks for copies from other
629 files in the commit that creates the file. When this
630 option is given three times, the command additionally
631 looks for copies from other files in any commit.
632 </p>
634 alphanumeric characters that git must detect as moving/copying
635 between files for it to associate those lines with the parent
636 commit. And the default value is 40. If there are more than one
638 take effect.</p></div>
639 </dd>
641 -h
642 </dt>
644 --help
645 </dt>
646 <dd>
647 <p>
648 Show help message.
649 </p>
650 </dd>
652 -c
653 </dt>
654 <dd>
655 <p>
657 </p>
658 </dd>
660 --score-debug
661 </dt>
662 <dd>
663 <p>
664 Include debugging information related to the movement of
667 This is the number of alphanumeric characters detected
668 as having been moved between or within files. This must be above
670 of code to have been moved.
671 </p>
672 </dd>
674 -f
675 </dt>
677 --show-name
678 </dt>
679 <dd>
680 <p>
681 Show the filename in the original commit. By default
682 the filename is shown if there is any line that came from a
683 file with a different name, due to rename detection.
684 </p>
685 </dd>
687 -n
688 </dt>
690 --show-number
691 </dt>
692 <dd>
693 <p>
694 Show the line number in the original commit (Default: off).
695 </p>
696 </dd>
698 -s
699 </dt>
700 <dd>
701 <p>
702 Suppress the author name and timestamp from the output.
703 </p>
704 </dd>
706 -e
707 </dt>
709 --show-email
710 </dt>
711 <dd>
712 <p>
713 Show the author email instead of author name (Default: off).
714 </p>
715 </dd>
717 -w
718 </dt>
719 <dd>
720 <p>
721 Ignore whitespace when comparing the parent’s version and
722 the child’s to find where the lines came from.
723 </p>
724 </dd>
725 </dl></div>
726 </div>
730 header at the minimum has the first line which has:</p></div>
732 <li>
733 <p>
735 </p>
736 </li>
737 <li>
738 <p>
739 the line number of the line in the original file;
740 </p>
741 </li>
742 <li>
743 <p>
744 the line number of the line in the final file;
745 </p>
746 </li>
747 <li>
748 <p>
749 on a line that starts a group of lines from a different
750 commit than the previous one, the number of lines in this
751 group. On subsequent lines this field is absent.
752 </p>
753 </li>
754 </ul></div>
756 at least once for each commit:</p></div>
758 <li>
759 <p>
762 for committer.
763 </p>
764 </li>
765 <li>
766 <p>
767 the filename in the commit that the line is attributed to.
768 </p>
769 </li>
770 <li>
771 <p>
772 the first line of the commit log message ("summary").
773 </p>
774 </li>
775 </ul></div>
777 header, prefixed by a TAB. This is to allow adding more
778 header elements later.</p></div>
779 </div>
782 <div class="paragraph"><p>Unlike <em>git blame</em> and <em>git annotate</em> in older versions of git, the extent
783 of the annotation can be limited to both line ranges and revision
784 ranges. When you are interested in finding the origin for
792 </div></div>
793 <div class="paragraph"><p>Also you can use a regular expression to specify the line range:</p></div>
797 </div></div>
798 <div class="paragraph"><p>which limits the annotation to the body of the <tt>hello</tt> subroutine.</p></div>
806 </div></div>
808 lines that have not changed since the range boundary (either the
810 weeks old in the above example) are blamed for that range
811 boundary commit.</p></div>
813 created by copy-and-paste from existing files. Sometimes this
814 indicates that the developer was being sloppy and did not
815 refactor the code properly. You can first find the commit that
816 introduced the file with:</p></div>
820 </div></div>
826 </div></div>
827 </div>
830 <div class="paragraph"><p>When called with <tt>--incremental</tt> option, the command outputs the
831 result as it is built. The output generally will talk about
832 lines touched by more recent commits first (i.e. the lines will
833 be annotated out of order) and is meant to be used by
834 interactive viewers.</p></div>
836 does not contain the actual lines from the file that is being
837 annotated.</p></div>
839 <li>
840 <p>
841 Each blame entry always starts with a line of:
842 </p>
845 <pre><tt><40-byte hex sha1> <sourceline> <resultline> <num_lines></tt></pre>
846 </div></div>
848 </li>
849 <li>
850 <p>
851 The first time that a commit shows up in the stream, it has various
852 other information about it printed out with a one-word tag at the
853 beginning of each line describing the extra commit information (author,
854 email, committer, dates, summary, etc.).
855 </p>
856 </li>
857 <li>
858 <p>
859 Unlike the Porcelain format, the filename information is always
860 given and terminates the entry:
861 </p>
865 </div></div>
866 <div class="paragraph"><p>and thus it is really quite easy to parse for some line- and word-oriented
867 parser (which should be quite natural for most scripting languages).</p></div>
869 <table><tr>
872 </td>
875 where you do not recognize the tag words (or care about that particular
876 one) at the beginning of the "extended information" lines. That way, if
877 there is ever added information (like the commit encoding or extended
878 commit commentary), a blame viewer will not care.</td>
879 </tr></table>
880 </div>
881 </li>
882 </ol></div>
883 </div>
886 <div class="paragraph"><p>If the file <tt>.mailmap</tt> exists at the toplevel of the repository, or at
887 the location pointed to by the mailmap.file configuration option, it
888 is used to map author and committer names and email addresses to
889 canonical real names and email addresses.</p></div>
891 real name of an author, whitespace, and an email address used in the
896 </div></div>
901 </div></div>
902 <div class="paragraph"><p>which allows mailmap to replace only the email part of a commit, and:</p></div>
906 </div></div>
908 commit matching the specified commit email address, and:</p></div>
912 </div></div>
914 commit matching both the specified commit name and email address.</p></div>
916 and Joe, whose names appear in the repository under several forms:</p></div>
924 </div></div>
927 would look like:</p></div>
932 </div></div>
933 <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
934 real name of that author is already correct.</p></div>
936 authors:</p></div>
945 </div></div>
946 <div class="paragraph"><p>Then you might want a <tt>.mailmap</tt> file that looks like:</p></div>
954 </div></div>
955 <div class="paragraph"><p>Use hash <em>#</em> for comments that are either on their own line, or after
956 the email address.</p></div>
957 </div>
961 </div>
964 <div class="paragraph"><p>Written by Junio C Hamano <<a href="mailto:gitster@pobox.com">gitster@pobox.com</a>></p></div>
965 </div>
969 </div>
973 </div>
974 </div>
975 </body>
976 </html>