| blob | 24b8df29a6fc25e92b295a0c900927c215eea780 |
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 }
129 }
133 }
135 /* Block element titles. */
143 }
146 }
150 }
153 }
156 }
162 }
168 }
176 }
181 }
185 }
189 }
190 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
193 }
202 }
206 }
211 }
217 dl {
220 }
221 dt {
226 }
229 }
233 }
236 }
239 }
242 }
245 }
248 }
255 }
259 }
263 }
264 tfoot {
266 }
269 }
272 }
273 /* Because the table frame attribute is overriden by CSS in most browsers. */
276 }
280 }
284 }
290 }
293 }
296 }
302 }
305 }
309 }
313 }
317 }
321 }
326 }
330 }
340 }
345 }
347 div#toc {
349 }
351 div#toctitle {
358 }
363 }
367 }
371 }
375 }
376 /* Overrides for manpage documents */
377 h1 {
382 }
383 h2 {
385 }
388 }
392 }
394 /* Workarounds for IE6's broken and incomplete CSS2. */
400 }
407 }
413 }
418 }
422 }
426 }
431 }
433 /* IE6 sets dynamically generated links as visited. */
435 </style>
437 /*<![CDATA[*/
441 /////////////////////////////////////////////////////////////////////
442 // Table Of Contents generator
443 /////////////////////////////////////////////////////////////////////
445 /* Author: Mihai Bazon, September 2002
446 * http://students.infoiasi.ro/~mishoo
447 *
448 * Table Of Content generator
449 * Version: 0.4
450 *
451 * Feel free to use this script under the terms of the GNU General Public
452 * License, as long as you do not remove or alter this notice.
453 */
455 /* modified by Troy D. Hanson, September 2006. License: GPL */
456 /* modified by Stuart Rackham, 2006, 2009. License: GPL */
458 // toclevels = 1..4.
468 }
470 }
476 }
481 // Function that scans the DOM tree for header elements (the DOM2
482 // nodeIterator API would be a better technique but not supported by all
483 // browsers).
490 }
492 }
493 }
494 }
497 }
512 }
515 },
518 /////////////////////////////////////////////////////////////////////
519 // Footnotes generator
520 /////////////////////////////////////////////////////////////////////
522 /* Based on footnote generation code from:
523 * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
524 */
534 n++;
535 // Use [\s\S] in place of . so multi-line matches work.
536 // Because JavaScript has no s (dotall) regex flag.
547 }
548 }
552 // Process footnoterefs.
561 }
562 }
563 }
564 }
566 }
567 /*]]>*/
568 </script>
569 </head>
570 <body>
572 <h1>
573 git-blame(1) Manual Page
574 </h1>
577 <p>git-blame -
578 Show what revision and author last modified each line of a file
579 </p>
580 </div>
581 </div>
586 <div class="verseblock-content"><em>git blame</em> [-c] [-b] [-l] [--root] [-t] [-f] [-n] [-s] [-e] [-p] [-w] [--incremental] [-L n,m]
590 </div></div>
591 </div>
594 <div class="paragraph"><p>Annotates each line in the given file with information from the revision which
595 last modified the line. Optionally, start annotating from the given revision.</p></div>
597 <div class="paragraph"><p>The report does not tell you anything about lines which have been deleted or
599 interface briefly mentioned in the following paragraph.</p></div>
600 <div class="paragraph"><p>Apart from supporting file annotation, git also supports searching the
601 development history for when a code snippet occurred in a change. This makes it
602 possible to track when a code snippet was added to a file, moved or copied
603 between files, and eventually deleted or replaced. It works by searching for
604 a text string in the diff. A small example:</p></div>
607 <pre><tt>$ git log --pretty=oneline -S'blame_usage'
609 ea4c7f9bf69e781dd0cd88d2bccb2bf5cc15c9a7 git-blame: Make the output</tt></pre>
610 </div></div>
611 </div>
616 -b
617 </dt>
618 <dd>
619 <p>
620 Show blank SHA-1 for boundary commits. This can also
622 </p>
623 </dd>
625 --root
626 </dt>
627 <dd>
628 <p>
629 Do not treat root commits as boundaries. This can also be
631 </p>
632 </dd>
634 --show-stats
635 </dt>
636 <dd>
637 <p>
638 Include additional statistics at the end of blame output.
639 </p>
640 </dd>
643 </dt>
644 <dd>
645 <p>
647 one of these forms:
648 </p>
650 <li>
651 <p>
652 number
653 </p>
656 </li>
657 <li>
658 <p>
659 /regex/
660 </p>
664 </li>
665 <li>
666 <p>
667 +offset or -offset
668 </p>
671 </li>
672 </ul></div>
673 </dd>
675 -l
676 </dt>
677 <dd>
678 <p>
679 Show long rev (Default: off).
680 </p>
681 </dd>
683 -t
684 </dt>
685 <dd>
686 <p>
687 Show raw timestamp (Default: off).
688 </p>
689 </dd>
692 </dt>
693 <dd>
694 <p>
695 Use revisions from revs-file instead of calling <a href="git-rev-list.html">git-rev-list(1)</a>.
696 </p>
697 </dd>
699 --reverse
700 </dt>
701 <dd>
702 <p>
703 Walk history forward instead of backward. Instead of showing
704 the revision in which a line appeared, this shows the last
705 revision in which a line has existed. This requires a range of
706 revision like START..END where the path to blame exists in
707 START.
708 </p>
709 </dd>
711 -p
712 </dt>
714 --porcelain
715 </dt>
716 <dd>
717 <p>
718 Show in a format designed for machine consumption.
719 </p>
720 </dd>
722 --line-porcelain
723 </dt>
724 <dd>
725 <p>
726 Show the porcelain format, but output commit information for
727 each line, not just the first time a commit is referenced.
728 Implies --porcelain.
729 </p>
730 </dd>
732 --incremental
733 </dt>
734 <dd>
735 <p>
736 Show the result incrementally in a format designed for
737 machine consumption.
738 </p>
739 </dd>
742 </dt>
743 <dd>
744 <p>
745 Specifies the encoding used to output author names
747 output unconverted data. For more information see the
749 manual page.
750 </p>
751 </dd>
754 </dt>
755 <dd>
756 <p>
758 changes starting backwards from the working tree copy.
759 This flag makes the command pretend as if the working
760 tree copy has the contents of the named file (specify
762 </p>
763 </dd>
766 </dt>
767 <dd>
768 <p>
769 The value is one of the following alternatives:
770 {relative,local,default,iso,rfc,short}. If --date is not
771 provided, the value of the blame.date config variable is
772 used. If the blame.date config variable is also not set, the
773 iso format is used. For more information, See the discussion
775 </p>
776 </dd>
779 </dt>
780 <dd>
781 <p>
782 Detect moved or copied lines within a file. When a commit
783 moves or copies a block of lines (e.g. the original file
784 has A and then B, and the commit changes it to B and then
786 the movement and typically blames the lines that were moved
787 up (i.e. B) to the parent and assigns blame to the lines that
788 were moved down (i.e. A) to the child commit. With this
789 option, both groups of lines are blamed on the parent by
790 running extra passes of inspection.
791 </p>
793 alphanumeric characters that git must detect as moving/copying
794 within a file for it to associate those lines with the parent
796 </dd>
799 </dt>
800 <dd>
801 <p>
803 files that were modified in the same commit. This is
804 useful when you reorganize your program and move code
805 around across files. When this option is given twice,
806 the command additionally looks for copies from other
807 files in the commit that creates the file. When this
808 option is given three times, the command additionally
809 looks for copies from other files in any commit.
810 </p>
812 alphanumeric characters that git must detect as moving/copying
813 between files for it to associate those lines with the parent
814 commit. And the default value is 40. If there are more than one
816 take effect.</p></div>
817 </dd>
819 -h
820 </dt>
821 <dd>
822 <p>
823 Show help message.
824 </p>
825 </dd>
827 -c
828 </dt>
829 <dd>
830 <p>
832 </p>
833 </dd>
835 --score-debug
836 </dt>
837 <dd>
838 <p>
839 Include debugging information related to the movement of
842 This is the number of alphanumeric characters detected
843 as having been moved between or within files. This must be above
845 of code to have been moved.
846 </p>
847 </dd>
849 -f
850 </dt>
852 --show-name
853 </dt>
854 <dd>
855 <p>
856 Show the filename in the original commit. By default
857 the filename is shown if there is any line that came from a
858 file with a different name, due to rename detection.
859 </p>
860 </dd>
862 -n
863 </dt>
865 --show-number
866 </dt>
867 <dd>
868 <p>
869 Show the line number in the original commit (Default: off).
870 </p>
871 </dd>
873 -s
874 </dt>
875 <dd>
876 <p>
877 Suppress the author name and timestamp from the output.
878 </p>
879 </dd>
881 -e
882 </dt>
884 --show-email
885 </dt>
886 <dd>
887 <p>
888 Show the author email instead of author name (Default: off).
889 </p>
890 </dd>
892 -w
893 </dt>
894 <dd>
895 <p>
896 Ignore whitespace when comparing the parent’s version and
897 the child’s to find where the lines came from.
898 </p>
899 </dd>
902 </dt>
903 <dd>
904 <p>
907 is used for a caret to mark the boundary commit.
908 </p>
909 </dd>
910 </dl></div>
911 </div>
915 header at the minimum has the first line which has:</p></div>
917 <li>
918 <p>
920 </p>
921 </li>
922 <li>
923 <p>
924 the line number of the line in the original file;
925 </p>
926 </li>
927 <li>
928 <p>
929 the line number of the line in the final file;
930 </p>
931 </li>
932 <li>
933 <p>
934 on a line that starts a group of lines from a different
935 commit than the previous one, the number of lines in this
936 group. On subsequent lines this field is absent.
937 </p>
938 </li>
939 </ul></div>
941 at least once for each commit:</p></div>
943 <li>
944 <p>
947 for committer.
948 </p>
949 </li>
950 <li>
951 <p>
952 the filename in the commit that the line is attributed to.
953 </p>
954 </li>
955 <li>
956 <p>
957 the first line of the commit log message ("summary").
958 </p>
959 </li>
960 </ul></div>
962 header, prefixed by a TAB. This is to allow adding more
963 header elements later.</p></div>
965 already been seen. For example, two lines that are blamed to the same
966 commit will both be shown, but the details for that commit will be shown
967 only once. This is more efficient, but may require more state be kept by
969 commit information for each line, allowing simpler (but less efficient)
970 usage like:</p></div>
973 <pre><tt># count the number of lines attributed to each author
974 git blame --line-porcelain file |
975 sed -n 's/^author //p' |
976 sort | uniq -c | sort -rn</tt></pre>
977 </div></div>
978 </div>
981 <div class="paragraph"><p>Unlike <em>git blame</em> and <em>git annotate</em> in older versions of git, the extent
982 of the annotation can be limited to both line ranges and revision
983 ranges. When you are interested in finding the origin for
991 </div></div>
992 <div class="paragraph"><p>Also you can use a regular expression to specify the line range:</p></div>
996 </div></div>
997 <div class="paragraph"><p>which limits the annotation to the body of the <tt>hello</tt> subroutine.</p></div>
1005 </div></div>
1007 lines that have not changed since the range boundary (either the
1009 weeks old in the above example) are blamed for that range
1010 boundary commit.</p></div>
1012 created by copy-and-paste from existing files. Sometimes this
1013 indicates that the developer was being sloppy and did not
1014 refactor the code properly. You can first find the commit that
1015 introduced the file with:</p></div>
1019 </div></div>
1025 </div></div>
1026 </div>
1029 <div class="paragraph"><p>When called with <tt>--incremental</tt> option, the command outputs the
1030 result as it is built. The output generally will talk about
1031 lines touched by more recent commits first (i.e. the lines will
1032 be annotated out of order) and is meant to be used by
1033 interactive viewers.</p></div>
1035 does not contain the actual lines from the file that is being
1036 annotated.</p></div>
1038 <li>
1039 <p>
1040 Each blame entry always starts with a line of:
1041 </p>
1044 <pre><tt><40-byte hex sha1> <sourceline> <resultline> <num_lines></tt></pre>
1045 </div></div>
1047 </li>
1048 <li>
1049 <p>
1050 The first time that a commit shows up in the stream, it has various
1051 other information about it printed out with a one-word tag at the
1052 beginning of each line describing the extra commit information (author,
1053 email, committer, dates, summary, etc.).
1054 </p>
1055 </li>
1056 <li>
1057 <p>
1058 Unlike the Porcelain format, the filename information is always
1059 given and terminates the entry:
1060 </p>
1064 </div></div>
1065 <div class="paragraph"><p>and thus it is really quite easy to parse for some line- and word-oriented
1066 parser (which should be quite natural for most scripting languages).</p></div>
1068 <table><tr>
1071 </td>
1074 where you do not recognize the tag words (or care about that particular
1075 one) at the beginning of the "extended information" lines. That way, if
1076 there is ever added information (like the commit encoding or extended
1077 commit commentary), a blame viewer will not care.</td>
1078 </tr></table>
1079 </div>
1080 </li>
1081 </ol></div>
1082 </div>
1085 <div class="paragraph"><p>If the file <tt>.mailmap</tt> exists at the toplevel of the repository, or at
1086 the location pointed to by the mailmap.file configuration option, it
1087 is used to map author and committer names and email addresses to
1088 canonical real names and email addresses.</p></div>
1090 real name of an author, whitespace, and an email address used in the
1091 commit (enclosed by <em><</em> and <em>></em>) to map to the name. For example:</p></div>
1095 </div></div>
1100 </div></div>
1101 <div class="paragraph"><p>which allows mailmap to replace only the email part of a commit, and:</p></div>
1105 </div></div>
1107 commit matching the specified commit email address, and:</p></div>
1111 </div></div>
1113 commit matching both the specified commit name and email address.</p></div>
1115 and Joe, whose names appear in the repository under several forms:</p></div>
1123 </div></div>
1126 would look like:</p></div>
1131 </div></div>
1132 <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
1133 real name of that author is already correct.</p></div>
1135 authors:</p></div>
1144 </div></div>
1145 <div class="paragraph"><p>Then you might want a <tt>.mailmap</tt> file that looks like:</p></div>
1153 </div></div>
1154 <div class="paragraph"><p>Use hash <em>#</em> for comments that are either on their own line, or after
1155 the email address.</p></div>
1156 </div>
1160 </div>
1164 </div>
1165 </div>
1170 </div>
1171 </div>
1172 </body>
1173 </html>