| blob | c05193cb2befc5fcb46ebd684b55e45e038d6b4d |
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-show(1) Manual Page
407 </h1>
410 <p>git-show -
411 Show various types of objects
412 </p>
413 </div>
414 </div>
418 </div>
423 presents the merge commit in a special format as produced by
425 <div class="paragraph"><p>For tags, it shows the tag message and the referenced objects.</p></div>
427 with --name-only).</p></div>
429 <div class="paragraph"><p>The command takes options applicable to the <em>git diff-tree</em> command to
430 control how the changes the commit introduces are shown.</p></div>
431 <div class="paragraph"><p>This manual page describes only the most frequently used options.</p></div>
432 </div>
438 </dt>
439 <dd>
440 <p>
441 The names of objects to show.
442 For a more complete list of ways to spell object names, see
444 </p>
445 </dd>
448 </dt>
451 </dt>
452 <dd>
453 <p>
454 Pretty-print the contents of the commit logs in a given format,
456 <em>full</em>, <em>fuller</em>, <em>email</em>, <em>raw</em> and <em>format:<string></em>. See
457 the "PRETTY FORMATS" section for some additional details for each
459 </p>
462 </dd>
464 --abbrev-commit
465 </dt>
466 <dd>
467 <p>
468 Instead of showing the full 40-byte hexadecimal commit object
469 name, show only a partial prefix. Non default number of
470 digits can be specified with "--abbrev=<n>" (which also modifies
471 diff output, if it is displayed).
472 </p>
475 </dd>
477 --oneline
478 </dt>
479 <dd>
480 <p>
481 This is a shorthand for "--pretty=oneline --abbrev-commit"
482 used together.
483 </p>
484 </dd>
487 </dt>
488 <dd>
489 <p>
490 The commit objects record the encoding used for the log message
491 in their encoding header; this option can be used to tell the
492 command to re-code the commit log message in the encoding
493 preferred by the user. For non plumbing commands this
494 defaults to UTF-8.
495 </p>
496 </dd>
498 --no-notes
499 </dt>
502 </dt>
503 <dd>
504 <p>
506 commit, when showing the commit log message. This is the default
509 given on the command line.
510 </p>
513 </dd>
515 --[no-]standard-notes
516 </dt>
517 <dd>
518 <p>
519 Enable or disable populating the notes ref list from the
521 corresponding environment overrides). Enabled by default.
523 </p>
524 </dd>
525 </dl></div>
526 </div>
532 "Merge: " and the sha1s of ancestral commits are printed,
533 separated by spaces. Note that the listed commits may not
535 have limited your view of history: for example, if you are
536 only interested in changes related to a certain directory or
537 file.</p></div>
540 config option to either another format name, or a
543 built-in formats:</p></div>
545 <li>
546 <p>
548 </p>
552 </div></div>
554 </li>
555 <li>
556 <p>
558 </p>
563 </div></div>
567 </div></div>
568 </li>
569 <li>
570 <p>
572 </p>
578 </div></div>
582 </div></div>
586 </div></div>
587 </li>
588 <li>
589 <p>
591 </p>
597 </div></div>
601 </div></div>
605 </div></div>
606 </li>
607 <li>
608 <p>
610 </p>
618 </div></div>
622 </div></div>
626 </div></div>
627 </li>
628 <li>
629 <p>
631 </p>
638 </div></div>
642 </div></div>
643 </li>
644 <li>
645 <p>
647 </p>
649 stored in the commit object. Notably, the SHA1s are
650 displayed in full, regardless of whether --abbrev or
652 true parent commits, without taking grafts nor history
653 simplification into account.</p></div>
654 </li>
655 <li>
656 <p>
658 </p>
659 <div class="paragraph"><p>The <em>format:<string></em> format allows you to specify which information
660 you want to show. It works a little bit like printf format,
663 <div class="paragraph"><p>E.g, <em>format:"The author of %h was %an, %ar%nThe title was >>%s<<%n"</em>
664 would show something like this:</p></div>
668 The title was >>t4119: test autocomputing -p<n> for traditional diff input.<<</tt></pre>
669 </div></div>
672 <li>
673 <p>
675 </p>
676 </li>
677 <li>
678 <p>
680 </p>
681 </li>
682 <li>
683 <p>
685 </p>
686 </li>
687 <li>
688 <p>
690 </p>
691 </li>
692 <li>
693 <p>
695 </p>
696 </li>
697 <li>
698 <p>
700 </p>
701 </li>
702 <li>
703 <p>
705 </p>
706 </li>
707 <li>
708 <p>
709 <em>%aN</em>: author name (respecting .mailmap, see <a href="git-shortlog.html">git-shortlog(1)</a> or <a href="git-blame.html">git-blame(1)</a>)
710 </p>
711 </li>
712 <li>
713 <p>
715 </p>
716 </li>
717 <li>
718 <p>
719 <em>%aE</em>: author email (respecting .mailmap, see <a href="git-shortlog.html">git-shortlog(1)</a> or <a href="git-blame.html">git-blame(1)</a>)
720 </p>
721 </li>
722 <li>
723 <p>
725 </p>
726 </li>
727 <li>
728 <p>
730 </p>
731 </li>
732 <li>
733 <p>
735 </p>
736 </li>
737 <li>
738 <p>
740 </p>
741 </li>
742 <li>
743 <p>
745 </p>
746 </li>
747 <li>
748 <p>
750 </p>
751 </li>
752 <li>
753 <p>
754 <em>%cN</em>: committer name (respecting .mailmap, see <a href="git-shortlog.html">git-shortlog(1)</a> or <a href="git-blame.html">git-blame(1)</a>)
755 </p>
756 </li>
757 <li>
758 <p>
760 </p>
761 </li>
762 <li>
763 <p>
764 <em>%cE</em>: committer email (respecting .mailmap, see <a href="git-shortlog.html">git-shortlog(1)</a> or <a href="git-blame.html">git-blame(1)</a>)
765 </p>
766 </li>
767 <li>
768 <p>
770 </p>
771 </li>
772 <li>
773 <p>
775 </p>
776 </li>
777 <li>
778 <p>
780 </p>
781 </li>
782 <li>
783 <p>
785 </p>
786 </li>
787 <li>
788 <p>
790 </p>
791 </li>
792 <li>
793 <p>
795 </p>
796 </li>
797 <li>
798 <p>
800 </p>
801 </li>
802 <li>
803 <p>
805 </p>
806 </li>
807 <li>
808 <p>
810 </p>
811 </li>
812 <li>
813 <p>
815 </p>
816 </li>
817 <li>
818 <p>
820 </p>
821 </li>
822 <li>
823 <p>
825 </p>
826 </li>
827 <li>
828 <p>
830 </p>
831 </li>
832 <li>
833 <p>
835 </p>
836 </li>
837 <li>
838 <p>
840 </p>
841 </li>
842 <li>
843 <p>
845 </p>
846 </li>
847 <li>
848 <p>
850 </p>
851 </li>
852 <li>
853 <p>
855 </p>
856 </li>
857 <li>
858 <p>
860 </p>
861 </li>
862 <li>
863 <p>
865 </p>
866 </li>
867 <li>
868 <p>
870 </p>
871 </li>
872 <li>
873 <p>
875 </p>
876 </li>
877 <li>
878 <p>
880 </p>
881 </li>
882 <li>
883 <p>
885 </p>
886 </li>
887 <li>
888 <p>
891 </p>
892 </li>
893 </ul></div>
894 </li>
895 </ul></div>
897 <table><tr>
900 </td>
903 insert an empty string unless we are traversing reflog entries (e.g., by
906 </tr></table>
907 </div>
908 <div class="paragraph"><p>If you add a <tt>+</tt> (plus sign) after <em>%</em> of a placeholder, a line-feed
909 is inserted immediately before the expansion if and only if the
910 placeholder expands to a non-empty string.</p></div>
911 <div class="paragraph"><p>If you add a <tt>-</tt> (minus sign) after <em>%</em> of a placeholder, line-feeds that
912 immediately precede the expansion are deleted if and only if the
913 placeholder expands to an empty string.</p></div>
915 is inserted immediately before the expansion if and only if the
916 placeholder expands to a non-empty string.</p></div>
918 <li>
919 <p>
921 </p>
922 <div class="paragraph"><p>The <em>tformat:</em> format works exactly like <em>format:</em>, except that it
924 other words, each commit has the message terminator character (usually a
925 newline) appended, rather than a separator placed between entries.
926 This means that the final entry of a single-line format will be properly
927 terminated with a new line, just as the "oneline" format does.
928 For example:</p></div>
932 | perl -pe '$_ .= " -- NO NEWLINE\n" unless /\n/'
933 4da45be
934 7134973 -- NO NEWLINE
937 | perl -pe '$_ .= " -- NO NEWLINE\n" unless /\n/'
938 4da45be
940 </div></div>
941 <div class="paragraph"><p>In addition, any unrecognized string that has a <tt>%</tt> in it is interpreted
943 equivalent:</p></div>
948 </div></div>
949 </li>
950 </ul></div>
951 </div>
956 git show v1.0.0
957 </dt>
958 <dd>
959 <p>
961 points at.
962 </p>
963 </dd>
965 git show v1.0.0^{tree}
966 </dt>
967 <dd>
968 <p>
970 </p>
971 </dd>
973 git show -s --format=%s v1.0.0^{commit}
974 </dt>
975 <dd>
976 <p>
977 Shows the subject of the commit pointed to by the
979 </p>
980 </dd>
982 git show next~10:Documentation/README
983 </dt>
984 <dd>
985 <p>
987 they were current in the 10th last commit of the branch
989 </p>
990 </dd>
992 git show master:Makefile master:t/Makefile
993 </dt>
994 <dd>
995 <p>
996 Concatenates the contents of said Makefiles in the head
998 </p>
999 </dd>
1000 </dl></div>
1001 </div>
1006 <li>
1007 <p>
1008 The pathnames recorded in the index and in the tree objects
1009 are treated as uninterpreted sequences of non-NUL bytes.
1010 What readdir(2) returns are what are recorded and compared
1011 with the data git keeps track of, which in turn are expected
1013 thing as pathname encoding translation.
1014 </p>
1015 </li>
1016 <li>
1017 <p>
1018 The contents of the blob objects are uninterpreted sequences
1019 of bytes. There is no encoding translation at the core
1020 level.
1021 </p>
1022 </li>
1023 <li>
1024 <p>
1025 The commit log messages are uninterpreted sequences of non-NUL
1026 bytes.
1027 </p>
1028 </li>
1029 </ul></div>
1031 in UTF-8, both the core and git Porcelain are designed not to
1032 force UTF-8 on projects. If all participants of a particular
1033 project find it more convenient to use legacy encodings, git
1034 does not forbid it. However, there are a few things to keep in
1035 mind.</p></div>
1037 <li>
1038 <p>
1040 a warning if the commit log message given to it does not look
1041 like a valid UTF-8 string, unless you explicitly say your
1042 project uses a legacy encoding. The way to say this is to
1044 </p>
1047 <pre><tt>[i18n]
1049 </div></div>
1052 help other people who look at them later. Lack of this header
1054 </li>
1055 <li>
1056 <p>
1059 log message into UTF-8 unless otherwise specified. You can
1060 specify the desired output encoding with
1062 </p>
1065 <pre><tt>[i18n]
1067 </div></div>
1070 </li>
1071 </ol></div>
1073 message when a commit is made to force UTF-8 at the commit
1074 object level, because re-coding to UTF-8 is not necessarily a
1075 reversible operation.</p></div>
1076 </div>
1080 </div>
1084 </div>
1085 </div>
1086 </body>
1087 </html>