| blob | 8349fcfec3f0e43a1e362f29cae3e21627a866b4 |
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-commit(1) Manual Page
574 </h1>
577 <p>git-commit -
578 Record changes to the repository
579 </p>
580 </div>
581 </div>
586 <div class="verseblock-content"><em>git commit</em> [-a | --interactive | --patch] [-s] [-v] [-u<mode>] [--amend]
593 </div></div>
594 </div>
598 with a log message from the user describing the changes.</p></div>
601 <li>
602 <p>
605 files must be "added");
606 </p>
607 </li>
608 <li>
609 <p>
612 </p>
613 </li>
614 <li>
615 <p>
617 case the commit will ignore changes staged in the index, and instead
618 record the current content of the listed files (which must already
619 be known to git);
620 </p>
621 </li>
622 <li>
623 <p>
625 "add" changes from all known files (i.e. all files that are already
626 listed in the index) and to automatically "rm" files in the index
627 that have been removed from the working tree, and then perform the
628 actual commit;
629 </p>
630 </li>
631 <li>
632 <p>
634 to decide one by one which files or hunks should be part of the commit,
637 </p>
638 </li>
639 </ol></div>
641 summary of what is included by any of the above for the next
642 commit by giving the same set of parameters (options and paths).</p></div>
645 </div>
650 -a
651 </dt>
653 --all
654 </dt>
655 <dd>
656 <p>
657 Tell the command to automatically stage files that have
658 been modified and deleted, but new files you have not
659 told git about are not affected.
660 </p>
661 </dd>
663 -p
664 </dt>
666 --patch
667 </dt>
668 <dd>
669 <p>
670 Use the interactive patch selection interface to chose
672 details.
673 </p>
674 </dd>
677 </dt>
680 </dt>
681 <dd>
682 <p>
683 Take an existing commit object, and reuse the log message
684 and the authorship information (including the timestamp)
685 when creating the commit.
686 </p>
687 </dd>
690 </dt>
693 </dt>
694 <dd>
695 <p>
697 the user can further edit the commit message.
698 </p>
699 </dd>
702 </dt>
703 <dd>
704 <p>
706 The commit message will be the subject line from the specified
708 for details.
709 </p>
710 </dd>
713 </dt>
714 <dd>
715 <p>
717 The commit message subject line is taken from the specified
718 commit with a prefix of "squash! ". Can be used with additional
721 </p>
722 </dd>
724 --reset-author
725 </dt>
726 <dd>
727 <p>
728 When used with -C/-c/--amend options, or when committing after a
729 a conflicting cherry-pick, declare that the authorship of the
730 resulting commit now belongs of the committer. This also renews
731 the author timestamp.
732 </p>
733 </dd>
735 --short
736 </dt>
737 <dd>
738 <p>
739 When doing a dry-run, give the output in the short-format. See
741 </p>
742 </dd>
744 --porcelain
745 </dt>
746 <dd>
747 <p>
748 When doing a dry-run, give the output in a porcelain-ready
751 </p>
752 </dd>
754 -z
755 </dt>
756 <dd>
757 <p>
759 entries in the status output with NUL, instead of LF. If no
761 </p>
762 </dd>
765 </dt>
768 </dt>
769 <dd>
770 <p>
772 read the message from the standard input.
773 </p>
774 </dd>
777 </dt>
778 <dd>
779 <p>
780 Override the commit author. Specify an explicit author using the
781 standard <tt>A U Thor <<a href="mailto:author@example.com">author@example.com</a>></tt> format. Otherwise <author>
782 is assumed to be a pattern and is used to search for an existing
784 the commit author is then copied from the first such commit found.
785 </p>
786 </dd>
789 </dt>
790 <dd>
791 <p>
792 Override the author date used in the commit.
793 </p>
794 </dd>
797 </dt>
800 </dt>
801 <dd>
802 <p>
804 </p>
805 </dd>
808 </dt>
811 </dt>
812 <dd>
813 <p>
814 Use the contents of the given file as the initial version
815 of the commit message. The editor is invoked and you can
816 make subsequent changes. If a message is specified using
819 </p>
820 </dd>
822 -s
823 </dt>
825 --signoff
826 </dt>
827 <dd>
828 <p>
829 Add Signed-off-by line by the committer at the end of the commit
830 log message.
831 </p>
832 </dd>
834 -n
835 </dt>
837 --no-verify
838 </dt>
839 <dd>
840 <p>
841 This option bypasses the pre-commit and commit-msg hooks.
843 </p>
844 </dd>
846 --allow-empty
847 </dt>
848 <dd>
849 <p>
850 Usually recording a commit that has the exact same tree as its
851 sole parent commit is a mistake, and the command prevents you
852 from making such a commit. This option bypasses the safety, and
853 is primarily for use by foreign SCM interface scripts.
854 </p>
855 </dd>
857 --allow-empty-message
858 </dt>
859 <dd>
860 <p>
861 Like --allow-empty this command is primarily for use by foreign
862 SCM interface scripts. It allows you to create a commit with an
863 empty commit message without using plumbing commands like
865 </p>
866 </dd>
869 </dt>
870 <dd>
871 <p>
872 This option sets how the commit message is cleaned up.
875 trailing empty lines and #commentary from the commit message
876 only if the message is to be edited. Otherwise only whitespace
880 </p>
881 </dd>
883 -e
884 </dt>
886 --edit
887 </dt>
888 <dd>
889 <p>
892 commit log message unmodified. This option lets you
893 further edit the message taken from these sources.
894 </p>
895 </dd>
897 --amend
898 </dt>
899 <dd>
900 <p>
901 Used to amend the tip of the current branch. Prepare the tree
902 object you would want to replace the latest commit as usual
903 (this includes the usual -i/-o and explicit paths), and the
904 commit log editor is seeded with the commit message from the
905 tip of the current branch. The commit you create replaces the
906 current tip — if it was a merge, it will have the parents of
907 the current tip as parents — so the current top commit is
908 discarded.
909 </p>
913 <pre><tt> $ git reset --soft HEAD^
914 $ ... do something else to come up with the right tree ...
915 $ git commit -c ORIG_HEAD</tt></pre>
916 </div></div>
919 amend a commit that has already been published. (See the "RECOVERING
921 </dd>
923 -i
924 </dt>
926 --include
927 </dt>
928 <dd>
929 <p>
930 Before making a commit out of staged contents so far,
931 stage the contents of paths given on the command line
932 as well. This is usually not what you want unless you
933 are concluding a conflicted merge.
934 </p>
935 </dd>
937 -o
938 </dt>
940 --only
941 </dt>
942 <dd>
943 <p>
944 Make a commit only from the paths specified on the
945 command line, disregarding any contents that have been
946 staged so far. This is the default mode of operation of
948 in which case this option can be omitted.
950 no paths need to be specified, which can be used to amend
951 the last commit without committing changes that have
952 already been staged.
953 </p>
954 </dd>
957 </dt>
960 </dt>
961 <dd>
962 <p>
963 Show untracked files.
964 </p>
965 <div class="paragraph"><p>The mode parameter is optional (defaults to <em>all</em>), and is used to
966 specify the handling of untracked files; when -u is not used, the
970 <li>
971 <p>
973 </p>
974 </li>
975 <li>
976 <p>
978 </p>
979 </li>
980 <li>
981 <p>
983 </p>
986 </li>
987 </ul></div>
988 </dd>
990 -v
991 </dt>
993 --verbose
994 </dt>
995 <dd>
996 <p>
997 Show unified diff between the HEAD commit and what
998 would be committed at the bottom of the commit message
999 template. Note that this diff output doesn’t have its
1001 </p>
1002 </dd>
1004 -q
1005 </dt>
1007 --quiet
1008 </dt>
1009 <dd>
1010 <p>
1011 Suppress commit summary message.
1012 </p>
1013 </dd>
1015 --dry-run
1016 </dt>
1017 <dd>
1018 <p>
1019 Do not create a commit, but show a list of paths that are
1020 to be committed, paths with local changes that will be left
1021 uncommitted and paths that are untracked.
1022 </p>
1023 </dd>
1025 --status
1026 </dt>
1027 <dd>
1028 <p>
1030 message template when using an editor to prepare the commit
1031 message. Defaults to on, but can be used to override
1032 configuration variable commit.status.
1033 </p>
1034 </dd>
1036 --no-status
1037 </dt>
1038 <dd>
1039 <p>
1041 commit message template when using an editor to prepare the
1042 default commit message.
1043 </p>
1044 </dd>
1046 --
1047 </dt>
1048 <dd>
1049 <p>
1050 Do not interpret any more arguments as options.
1051 </p>
1052 </dd>
1055 </dt>
1056 <dd>
1057 <p>
1058 When files are given on the command line, the command
1059 commits the contents of the named files, without
1060 recording the changes already staged. The contents of
1061 these files are also staged for the next commit on top
1062 of what have been staged before.
1063 </p>
1064 </dd>
1065 </dl></div>
1066 </div>
1071 support the following date formats:</p></div>
1074 Git internal format
1075 </dt>
1076 <dd>
1077 <p>
1082 </p>
1083 </dd>
1085 RFC 2822
1086 </dt>
1087 <dd>
1088 <p>
1089 The standard email format as described by RFC 2822, for example
1091 </p>
1092 </dd>
1094 ISO 8601
1095 </dt>
1096 <dd>
1097 <p>
1098 Time and date specified by the ISO 8601 standard, for example
1101 </p>
1103 <table><tr>
1106 </td>
1109 </tr></table>
1110 </div>
1111 </dd>
1112 </dl></div>
1113 </div>
1117 your working tree are temporarily stored to a staging area
1119 reverted back, only in the index but not in the working tree,
1122 this file from participating in the next commit. After building
1123 the state to be committed incrementally with these commands,
1125 has been staged so far. This is the most basic form of the
1126 command. An example:</p></div>
1129 <pre><tt>$ edit hello.c
1130 $ git rm goodbye.c
1131 $ git add hello.c
1132 $ git commit</tt></pre>
1133 </div></div>
1136 contents are tracked in
1138 for you. That is, this example does the same as the earlier
1139 example if there is no other change in your working tree:</p></div>
1142 <pre><tt>$ edit hello.c
1143 $ rm goodbye.c
1144 $ git commit -a</tt></pre>
1145 </div></div>
1147 notices that you have modified hello.c and removed goodbye.c,
1151 When pathnames are given, the command makes a commit that
1152 only records the changes made to the named paths:</p></div>
1155 <pre><tt>$ edit hello.c hello.h
1156 $ git add hello.c hello.h
1157 $ edit Makefile
1158 $ git commit Makefile</tt></pre>
1159 </div></div>
1160 <div class="paragraph"><p>This makes a commit that records the modification to <tt>Makefile</tt>.
1162 in the resulting commit. However, their changes are not lost — they are still staged and merely held back. After the above
1163 sequence, if you do:</p></div>
1167 </div></div>
1170 <div class="paragraph"><p>After a merge (initiated by <em>git merge</em> or <em>git pull</em>) stops
1171 because of conflicts, cleanly merged
1172 paths are already staged to be committed for you, and paths that
1173 conflicted are left in unmerged state. You would have to first
1175 and after fixing them manually in your working tree, you would
1179 <pre><tt>$ git status | grep unmerged
1180 unmerged: hello.c
1181 $ edit hello.c
1182 $ git add hello.c</tt></pre>
1183 </div></div>
1184 <div class="paragraph"><p>After resolving conflicts and staging the result, <tt>git ls-files -u</tt>
1185 would stop mentioning the conflicted path. When you are done,
1190 </div></div>
1192 option to save typing. One difference is that during a merge
1194 alter the order the changes are committed, because the merge
1195 should be recorded as a single commit. In fact, the command
1197 </div>
1200 <div class="paragraph"><p>Though not required, it’s a good idea to begin the commit message
1201 with a single short (less than 50 character) line summarizing the
1202 change, followed by a blank line and then a more thorough description.
1203 Tools that turn commits into email, for example, use the first line
1204 on the Subject: line and the rest of the commit in the body.</p></div>
1207 <li>
1208 <p>
1209 The pathnames recorded in the index and in the tree objects
1210 are treated as uninterpreted sequences of non-NUL bytes.
1211 What readdir(2) returns are what are recorded and compared
1212 with the data git keeps track of, which in turn are expected
1214 thing as pathname encoding translation.
1215 </p>
1216 </li>
1217 <li>
1218 <p>
1219 The contents of the blob objects are uninterpreted sequences
1220 of bytes. There is no encoding translation at the core
1221 level.
1222 </p>
1223 </li>
1224 <li>
1225 <p>
1226 The commit log messages are uninterpreted sequences of non-NUL
1227 bytes.
1228 </p>
1229 </li>
1230 </ul></div>
1232 in UTF-8, both the core and git Porcelain are designed not to
1233 force UTF-8 on projects. If all participants of a particular
1234 project find it more convenient to use legacy encodings, git
1235 does not forbid it. However, there are a few things to keep in
1236 mind.</p></div>
1238 <li>
1239 <p>
1241 a warning if the commit log message given to it does not look
1242 like a valid UTF-8 string, unless you explicitly say your
1243 project uses a legacy encoding. The way to say this is to
1245 </p>
1248 <pre><tt>[i18n]
1250 </div></div>
1253 help other people who look at them later. Lack of this header
1255 </li>
1256 <li>
1257 <p>
1260 log message into UTF-8 unless otherwise specified. You can
1261 specify the desired output encoding with
1263 </p>
1266 <pre><tt>[i18n]
1268 </div></div>
1271 </li>
1272 </ol></div>
1274 message when a commit is made to force UTF-8 at the commit
1275 object level, because re-coding to UTF-8 is not necessarily a
1276 reversible operation.</p></div>
1277 </div>
1280 <div class="paragraph"><p>The editor used to edit the commit log message will be chosen from the
1281 GIT_EDITOR environment variable, the core.editor configuration variable, the
1282 VISUAL environment variable, or the EDITOR environment variable (in that
1284 </div>
1287 <div class="paragraph"><p>This command can run <tt>commit-msg</tt>, <tt>prepare-commit-msg</tt>, <tt>pre-commit</tt>,
1289 information.</p></div>
1290 </div>
1298 </div>
1302 </div>
1303 </div>
1308 </div>
1309 </div>
1310 </body>
1311 </html>