| blob | 4db79765b2aaaf610016273d9bd93901e9f450e4 |
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>
420 </div></div>
421 </div>
426 presents the merge commit in a special format as produced by
428 <div class="paragraph"><p>For tags, it shows the tag message and the referenced objects.</p></div>
430 with --name-only).</p></div>
432 <div class="paragraph"><p>The command takes options applicable to the <em>git diff-tree</em> command to
433 control how the changes the commit introduces are shown.</p></div>
434 <div class="paragraph"><p>This manual page describes only the most frequently used options.</p></div>
435 </div>
441 </dt>
442 <dd>
443 <p>
444 The names of objects to show.
445 For a more complete list of ways to spell object names, see
447 </p>
448 </dd>
451 </dt>
454 </dt>
455 <dd>
456 <p>
457 Pretty-print the contents of the commit logs in a given format,
459 <em>full</em>, <em>fuller</em>, <em>email</em>, <em>raw</em> and <em>format:<string></em>. See
460 the "PRETTY FORMATS" section for some additional details for each
462 </p>
465 </dd>
467 --abbrev-commit
468 </dt>
469 <dd>
470 <p>
471 Instead of showing the full 40-byte hexadecimal commit object
472 name, show only a partial prefix. Non default number of
473 digits can be specified with "--abbrev=<n>" (which also modifies
474 diff output, if it is displayed).
475 </p>
478 </dd>
480 --no-abbrev-commit
481 </dt>
482 <dd>
483 <p>
484 Show the full 40-byte hexadecimal commit object name. This negates
487 </p>
488 </dd>
490 --oneline
491 </dt>
492 <dd>
493 <p>
494 This is a shorthand for "--pretty=oneline --abbrev-commit"
495 used together.
496 </p>
497 </dd>
500 </dt>
501 <dd>
502 <p>
503 The commit objects record the encoding used for the log message
504 in their encoding header; this option can be used to tell the
505 command to re-code the commit log message in the encoding
506 preferred by the user. For non plumbing commands this
507 defaults to UTF-8.
508 </p>
509 </dd>
512 </dt>
513 <dd>
514 <p>
516 commit, when showing the commit log message. This is the default
519 on the command line.
520 </p>
523 environment overrides). See <a href="git-config.html">git-config(1)</a> for more details.</p></div>
524 <div class="paragraph"><p>With an optional <em><ref></em> argument, show this notes ref instead of the
526 is not qualified.</p></div>
528 being displayed. Examples: "--notes=foo" will show only notes from
531 </dd>
533 --no-notes
534 </dt>
535 <dd>
536 <p>
538 resetting the list of notes refs from which notes are shown.
539 Options are parsed in the order given on the command line, so e.g.
540 "--notes --notes=foo --no-notes --notes=bar" will only show notes
541 from "refs/notes/bar".
542 </p>
543 </dd>
546 </dt>
548 --[no-]standard-notes
549 </dt>
550 <dd>
551 <p>
552 These options are deprecated. Use the above --notes/--no-notes
553 options instead.
554 </p>
555 </dd>
556 </dl></div>
557 </div>
563 "Merge: " and the sha1s of ancestral commits are printed,
564 separated by spaces. Note that the listed commits may not
566 have limited your view of history: for example, if you are
567 only interested in changes related to a certain directory or
568 file.</p></div>
571 config option to either another format name, or a
574 built-in formats:</p></div>
576 <li>
577 <p>
579 </p>
583 </div></div>
585 </li>
586 <li>
587 <p>
589 </p>
594 </div></div>
598 </div></div>
599 </li>
600 <li>
601 <p>
603 </p>
609 </div></div>
613 </div></div>
617 </div></div>
618 </li>
619 <li>
620 <p>
622 </p>
628 </div></div>
632 </div></div>
636 </div></div>
637 </li>
638 <li>
639 <p>
641 </p>
649 </div></div>
653 </div></div>
657 </div></div>
658 </li>
659 <li>
660 <p>
662 </p>
669 </div></div>
673 </div></div>
674 </li>
675 <li>
676 <p>
678 </p>
680 stored in the commit object. Notably, the SHA1s are
681 displayed in full, regardless of whether --abbrev or
683 true parent commits, without taking grafts nor history
684 simplification into account.</p></div>
685 </li>
686 <li>
687 <p>
689 </p>
690 <div class="paragraph"><p>The <em>format:<string></em> format allows you to specify which information
691 you want to show. It works a little bit like printf format,
694 <div class="paragraph"><p>E.g, <em>format:"The author of %h was %an, %ar%nThe title was >>%s<<%n"</em>
695 would show something like this:</p></div>
699 The title was >>t4119: test autocomputing -p<n> for traditional diff input.<<</tt></pre>
700 </div></div>
703 <li>
704 <p>
706 </p>
707 </li>
708 <li>
709 <p>
711 </p>
712 </li>
713 <li>
714 <p>
716 </p>
717 </li>
718 <li>
719 <p>
721 </p>
722 </li>
723 <li>
724 <p>
726 </p>
727 </li>
728 <li>
729 <p>
731 </p>
732 </li>
733 <li>
734 <p>
736 </p>
737 </li>
738 <li>
739 <p>
740 <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>)
741 </p>
742 </li>
743 <li>
744 <p>
746 </p>
747 </li>
748 <li>
749 <p>
750 <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>)
751 </p>
752 </li>
753 <li>
754 <p>
756 </p>
757 </li>
758 <li>
759 <p>
761 </p>
762 </li>
763 <li>
764 <p>
766 </p>
767 </li>
768 <li>
769 <p>
771 </p>
772 </li>
773 <li>
774 <p>
776 </p>
777 </li>
778 <li>
779 <p>
781 </p>
782 </li>
783 <li>
784 <p>
785 <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>)
786 </p>
787 </li>
788 <li>
789 <p>
791 </p>
792 </li>
793 <li>
794 <p>
795 <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>)
796 </p>
797 </li>
798 <li>
799 <p>
801 </p>
802 </li>
803 <li>
804 <p>
806 </p>
807 </li>
808 <li>
809 <p>
811 </p>
812 </li>
813 <li>
814 <p>
816 </p>
817 </li>
818 <li>
819 <p>
821 </p>
822 </li>
823 <li>
824 <p>
826 </p>
827 </li>
828 <li>
829 <p>
831 </p>
832 </li>
833 <li>
834 <p>
836 </p>
837 </li>
838 <li>
839 <p>
841 </p>
842 </li>
843 <li>
844 <p>
846 </p>
847 </li>
848 <li>
849 <p>
851 </p>
852 </li>
853 <li>
854 <p>
856 </p>
857 </li>
858 <li>
859 <p>
861 </p>
862 </li>
863 <li>
864 <p>
866 </p>
867 </li>
868 <li>
869 <p>
871 </p>
872 </li>
873 <li>
874 <p>
876 </p>
877 </li>
878 <li>
879 <p>
881 </p>
882 </li>
883 <li>
884 <p>
886 </p>
887 </li>
888 <li>
889 <p>
891 </p>
892 </li>
893 <li>
894 <p>
896 </p>
897 </li>
898 <li>
899 <p>
901 </p>
902 </li>
903 <li>
904 <p>
906 </p>
907 </li>
908 <li>
909 <p>
911 </p>
912 </li>
913 <li>
914 <p>
916 </p>
917 </li>
918 <li>
919 <p>
922 </p>
923 </li>
924 </ul></div>
925 </li>
926 </ul></div>
928 <table><tr>
931 </td>
934 insert an empty string unless we are traversing reflog entries (e.g., by
937 </tr></table>
938 </div>
939 <div class="paragraph"><p>If you add a <tt>+</tt> (plus sign) after <em>%</em> of a placeholder, a line-feed
940 is inserted immediately before the expansion if and only if the
941 placeholder expands to a non-empty string.</p></div>
942 <div class="paragraph"><p>If you add a <tt>-</tt> (minus sign) after <em>%</em> of a placeholder, line-feeds that
943 immediately precede the expansion are deleted if and only if the
944 placeholder expands to an empty string.</p></div>
946 is inserted immediately before the expansion if and only if the
947 placeholder expands to a non-empty string.</p></div>
949 <li>
950 <p>
952 </p>
953 <div class="paragraph"><p>The <em>tformat:</em> format works exactly like <em>format:</em>, except that it
955 other words, each commit has the message terminator character (usually a
956 newline) appended, rather than a separator placed between entries.
957 This means that the final entry of a single-line format will be properly
958 terminated with a new line, just as the "oneline" format does.
959 For example:</p></div>
963 | perl -pe '$_ .= " -- NO NEWLINE\n" unless /\n/'
964 4da45be
965 7134973 -- NO NEWLINE
968 | perl -pe '$_ .= " -- NO NEWLINE\n" unless /\n/'
969 4da45be
971 </div></div>
972 <div class="paragraph"><p>In addition, any unrecognized string that has a <tt>%</tt> in it is interpreted
974 equivalent:</p></div>
979 </div></div>
980 </li>
981 </ul></div>
982 </div>
988 </dt>
989 <dd>
990 <p>
992 points at.
993 </p>
994 </dd>
997 </dt>
998 <dd>
999 <p>
1001 </p>
1002 </dd>
1005 </dt>
1006 <dd>
1007 <p>
1008 Shows the subject of the commit pointed to by the
1010 </p>
1011 </dd>
1014 </dt>
1015 <dd>
1016 <p>
1018 they were current in the 10th last commit of the branch
1020 </p>
1021 </dd>
1024 </dt>
1025 <dd>
1026 <p>
1027 Concatenates the contents of said Makefiles in the head
1029 </p>
1030 </dd>
1031 </dl></div>
1032 </div>
1037 <li>
1038 <p>
1039 The pathnames recorded in the index and in the tree objects
1040 are treated as uninterpreted sequences of non-NUL bytes.
1041 What readdir(2) returns are what are recorded and compared
1042 with the data git keeps track of, which in turn are expected
1044 thing as pathname encoding translation.
1045 </p>
1046 </li>
1047 <li>
1048 <p>
1049 The contents of the blob objects are uninterpreted sequences
1050 of bytes. There is no encoding translation at the core
1051 level.
1052 </p>
1053 </li>
1054 <li>
1055 <p>
1056 The commit log messages are uninterpreted sequences of non-NUL
1057 bytes.
1058 </p>
1059 </li>
1060 </ul></div>
1062 in UTF-8, both the core and git Porcelain are designed not to
1063 force UTF-8 on projects. If all participants of a particular
1064 project find it more convenient to use legacy encodings, git
1065 does not forbid it. However, there are a few things to keep in
1066 mind.</p></div>
1068 <li>
1069 <p>
1071 a warning if the commit log message given to it does not look
1072 like a valid UTF-8 string, unless you explicitly say your
1073 project uses a legacy encoding. The way to say this is to
1075 </p>
1078 <pre><tt>[i18n]
1080 </div></div>
1083 help other people who look at them later. Lack of this header
1085 </li>
1086 <li>
1087 <p>
1090 log message into UTF-8 unless otherwise specified. You can
1091 specify the desired output encoding with
1093 </p>
1096 <pre><tt>[i18n]
1098 </div></div>
1101 </li>
1102 </ol></div>
1104 message when a commit is made to force UTF-8 at the commit
1105 object level, because re-coding to UTF-8 is not necessarily a
1106 reversible operation.</p></div>
1107 </div>
1111 </div>
1115 </div>
1116 </div>
1117 </body>
1118 </html>