| blob | d180049d02a5bbaca6294a64e7e3ebe49ffe59f0 |
4 <head>
8 /* Debug borders */
10 /*
11 border: 1px solid red;
12 */
13 }
15 body {
17 }
19 a {
22 }
25 }
27 em {
29 }
31 strong {
33 }
35 tt {
37 }
45 }
49 }
50 h2 {
52 }
53 h3 {
55 }
56 h3 + * {
58 }
63 }
65 hr {
67 }
69 p {
72 }
74 pre {
77 }
79 span#author {
84 }
85 span#email {
86 }
87 span#revision {
89 }
91 div#footer {
97 }
98 div#footer-text {
101 }
102 div#footer-badges {
105 }
107 div#preamble,
114 }
118 }
122 }
124 /* Block element titles. */
131 }
134 }
138 }
141 }
144 }
150 }
154 }
159 }
163 }
167 }
170 }
179 }
183 }
188 }
192 }
198 dl {
201 }
202 dt {
206 }
209 }
213 }
216 }
220 }
221 thead {
224 }
225 tfoot {
227 }
232 }
235 }
240 }
243 }
247 }
249 div#toctitle {
256 }
261 }
265 }
269 }
273 }
275 /* Workarounds for IE6's broken and incomplete CSS2. */
281 }
287 }
293 }
297 }
302 }
304 /* IE6 sets dynamically generated links as visited. */
306 </style>
308 </head>
309 <body>
311 <h1>
312 git-blame(1) Manual Page
313 </h1>
316 <p>git-blame -
317 Show what revision and author last modified each line of a file
318 </p>
319 </div>
320 </div>
324 <div class="content"><em>git blame</em> [-c] [-b] [-l] [--root] [-t] [-f] [-n] [-s] [-p] [-w] [--incremental] [-L n,m]
327 </div>
330 <div class="para"><p>Annotates each line in the given file with information from the revision which
331 last modified the line. Optionally, start annotating from the given revision.</p></div>
333 <div class="para"><p>The report does not tell you anything about lines which have been deleted or
335 interface briefly mentioned in the following paragraph.</p></div>
337 development history for when a code snippet occurred in a change. This makes it
338 possible to track when a code snippet was added to a file, moved or copied
339 between files, and eventually deleted or replaced. It works by searching for
340 a text string in the diff. A small example:</p></div>
343 <pre><tt>$ git log --pretty=oneline -S'blame_usage'
345 ea4c7f9bf69e781dd0cd88d2bccb2bf5cc15c9a7 git-blame: Make the output</tt></pre>
346 </div></div>
347 </div>
351 <dt>
352 -b
353 </dt>
354 <dd>
355 <p>
356 Show blank SHA-1 for boundary commits. This can also
358 </p>
359 </dd>
360 <dt>
361 --root
362 </dt>
363 <dd>
364 <p>
365 Do not treat root commits as boundaries. This can also be
367 </p>
368 </dd>
369 <dt>
370 --show-stats
371 </dt>
372 <dd>
373 <p>
374 Include additional statistics at the end of blame output.
375 </p>
376 </dd>
377 <dt>
379 </dt>
380 <dd>
381 <p>
383 one of these forms:
384 </p>
386 <li>
387 <p>
388 number
389 </p>
392 </li>
393 <li>
394 <p>
395 /regex/
396 </p>
400 </li>
401 <li>
402 <p>
403 +offset or -offset
404 </p>
407 </li>
408 </ul></div>
409 </dd>
410 <dt>
411 -l
412 </dt>
413 <dd>
414 <p>
415 Show long rev (Default: off).
416 </p>
417 </dd>
418 <dt>
419 -t
420 </dt>
421 <dd>
422 <p>
423 Show raw timestamp (Default: off).
424 </p>
425 </dd>
426 <dt>
428 </dt>
429 <dd>
430 <p>
431 Use revisions from revs-file instead of calling <a href="git-rev-list.html">git-rev-list(1)</a>.
432 </p>
433 </dd>
434 <dt>
435 --reverse
436 </dt>
437 <dd>
438 <p>
439 Walk history forward instead of backward. Instead of showing
440 the revision in which a line appeared, this shows the last
441 revision in which a line has existed. This requires a range of
442 revision like START..END where the path to blame exists in
443 START.
444 </p>
445 </dd>
446 <dt>
447 -p
448 </dt>
449 <dt>
450 --porcelain
451 </dt>
452 <dd>
453 <p>
454 Show in a format designed for machine consumption.
455 </p>
456 </dd>
457 <dt>
458 --incremental
459 </dt>
460 <dd>
461 <p>
462 Show the result incrementally in a format designed for
463 machine consumption.
464 </p>
465 </dd>
466 <dt>
468 </dt>
469 <dd>
470 <p>
471 Specifies the encoding used to output author names
473 output unconverted data. For more information see the
475 manual page.
476 </p>
477 </dd>
478 <dt>
480 </dt>
481 <dd>
482 <p>
484 changes starting backwards from the working tree copy.
485 This flag makes the command pretend as if the working
486 tree copy has the contents of the named file (specify
488 </p>
489 </dd>
490 <dt>
492 </dt>
493 <dd>
494 <p>
495 The value is one of the following alternatives:
496 {relative,local,default,iso,rfc,short}. If --date is not
497 provided, the value of the blame.date config variable is
498 used. If the blame.date config variable is also not set, the
499 iso format is used. For more information, See the discussion
501 </p>
502 </dd>
503 <dt>
505 </dt>
506 <dd>
507 <p>
508 Detect moving lines in the file as well. When a commit
509 moves a block of lines in a file (e.g. the original file
510 has A and then B, and the commit changes it to B and
512 the lines that were moved up (i.e. B) to the parent and
513 assigns blame to the lines that were moved down (i.e. A)
514 to the child commit. With this option, both groups of lines
515 are blamed on the parent.
516 </p>
518 alphanumeric characters that git must detect as moving
519 within a file for it to associate those lines with the parent
520 commit.</p></div>
521 </dd>
522 <dt>
524 </dt>
525 <dd>
526 <p>
528 files that were modified in the same commit. This is
529 useful when you reorganize your program and move code
530 around across files. When this option is given twice,
531 the command additionally looks for copies from other
532 files in the commit that creates the file. When this
533 option is given three times, the command additionally
534 looks for copies from other files in any commit.
535 </p>
537 alphanumeric characters that git must detect as moving
538 between files for it to associate those lines with the parent
539 commit.</p></div>
540 </dd>
541 <dt>
542 -h
543 </dt>
544 <dt>
545 --help
546 </dt>
547 <dd>
548 <p>
549 Show help message.
550 </p>
551 </dd>
552 <dt>
553 -c
554 </dt>
555 <dd>
556 <p>
558 </p>
559 </dd>
560 <dt>
561 --score-debug
562 </dt>
563 <dd>
564 <p>
565 Include debugging information related to the movement of
568 This is the number of alphanumeric characters detected
569 as having been moved between or within files. This must be above
571 of code to have been moved.
572 </p>
573 </dd>
574 <dt>
575 -f
576 </dt>
577 <dt>
578 --show-name
579 </dt>
580 <dd>
581 <p>
582 Show the filename in the original commit. By default
583 the filename is shown if there is any line that came from a
584 file with a different name, due to rename detection.
585 </p>
586 </dd>
587 <dt>
588 -n
589 </dt>
590 <dt>
591 --show-number
592 </dt>
593 <dd>
594 <p>
595 Show the line number in the original commit (Default: off).
596 </p>
597 </dd>
598 <dt>
599 -s
600 </dt>
601 <dd>
602 <p>
603 Suppress the author name and timestamp from the output.
604 </p>
605 </dd>
606 <dt>
607 -w
608 </dt>
609 <dd>
610 <p>
611 Ignore whitespace when comparing the parent's version and
612 the child's to find where the lines came from.
613 </p>
614 </dd>
615 </dl></div>
616 </div>
620 header at the minimum has the first line which has:</p></div>
622 <li>
623 <p>
625 </p>
626 </li>
627 <li>
628 <p>
629 the line number of the line in the original file;
630 </p>
631 </li>
632 <li>
633 <p>
634 the line number of the line in the final file;
635 </p>
636 </li>
637 <li>
638 <p>
639 on a line that starts a group of lines from a different
640 commit than the previous one, the number of lines in this
641 group. On subsequent lines this field is absent.
642 </p>
643 </li>
644 </ul></div>
646 at least once for each commit:</p></div>
648 <li>
649 <p>
652 for committer.
653 </p>
654 </li>
655 <li>
656 <p>
657 the filename in the commit that the line is attributed to.
658 </p>
659 </li>
660 <li>
661 <p>
662 the first line of the commit log message ("summary").
663 </p>
664 </li>
665 </ul></div>
667 header, prefixed by a TAB. This is to allow adding more
668 header elements later.</p></div>
669 </div>
672 <div class="para"><p>Unlike <em>git blame</em> and <em>git annotate</em> in older versions of git, the extent
673 of the annotation can be limited to both line ranges and revision
674 ranges. When you are interested in finding the origin for
682 </div></div>
687 </div></div>
688 <div class="para"><p>which limits the annotation to the body of the <tt>hello</tt> subroutine.</p></div>
696 </div></div>
698 lines that have not changed since the range boundary (either the
700 weeks old in the above example) are blamed for that range
701 boundary commit.</p></div>
703 created by copy-and-paste from existing files. Sometimes this
704 indicates that the developer was being sloppy and did not
705 refactor the code properly. You can first find the commit that
706 introduced the file with:</p></div>
710 </div></div>
716 </div></div>
717 </div>
721 result as it is built. The output generally will talk about
722 lines touched by more recent commits first (i.e. the lines will
723 be annotated out of order) and is meant to be used by
724 interactive viewers.</p></div>
726 does not contain the actual lines from the file that is being
727 annotated.</p></div>
729 <li>
730 <p>
731 Each blame entry always starts with a line of:
732 </p>
735 <pre><tt><40-byte hex sha1> <sourceline> <resultline> <num_lines></tt></pre>
736 </div></div>
738 </li>
739 <li>
740 <p>
741 The first time that a commit shows up in the stream, it has various
742 other information about it printed out with a one-word tag at the
743 beginning of each line describing the extra commit information (author,
744 email, committer, dates, summary, etc.).
745 </p>
746 </li>
747 <li>
748 <p>
749 Unlike the Porcelain format, the filename information is always
750 given and terminates the entry:
751 </p>
755 </div></div>
757 parser (which should be quite natural for most scripting languages).</p></div>
759 <table><tr>
762 </td>
765 where you do not recognize the tag words (or care about that particular
766 one) at the beginning of the "extended information" lines. That way, if
767 there is ever added information (like the commit encoding or extended
768 commit commentary), a blame viewer will not care.</td>
769 </tr></table>
770 </div>
771 </li>
772 </ol></div>
773 </div>
776 <div class="para"><p>If the file <tt>.mailmap</tt> exists at the toplevel of the repository, or at
777 the location pointed to by the mailmap.file configuration option, it
778 is used to map author and committer names and email addresses to
779 canonical real names and email addresses.</p></div>
781 real name of an author, whitespace, and an email address used in the
786 </div></div>
791 </div></div>
792 <div class="para"><p>which allows mailmap to replace only the email part of a commit, and:</p></div>
796 </div></div>
798 commit matching the specified commit email address, and:</p></div>
802 </div></div>
804 commit matching both the specified commit name and email address.</p></div>
806 and Joe, whose names appear in the repository under several forms:</p></div>
814 </div></div>
817 would look like:</p></div>
822 </div></div>
823 <div class="para"><p>Note how there is no need for an entry for <jane@laptop.(none)>, because the
824 real name of that author is already correct.</p></div>
826 authors:</p></div>
835 </div></div>
844 </div></div>
845 <div class="para"><p>Use hash <em>#</em> for comments that are either on their own line, or after
846 the email address.</p></div>
847 </div>
851 </div>
855 </div>
859 </div>
863 </div>
864 </div>
865 </body>
866 </html>