| blob | eba951806b17838f87407e5645ba7d1a5aae1097 |
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-status(1) Manual Page
574 </h1>
577 <p>git-status -
578 Show the working tree status
579 </p>
580 </div>
581 </div>
586 <div class="verseblock-content"><em>git status</em> [<options>…] [--] [<pathspec>…]</div>
588 </div></div>
589 </div>
593 current HEAD commit, paths that have differences between the working
594 tree and the index file, and paths in the working tree that are not
599 </div>
604 -s
605 </dt>
607 --short
608 </dt>
609 <dd>
610 <p>
611 Give the output in the short-format.
612 </p>
613 </dd>
615 -b
616 </dt>
618 --branch
619 </dt>
620 <dd>
621 <p>
622 Show the branch and tracking info even in short-format.
623 </p>
624 </dd>
626 --porcelain
627 </dt>
628 <dd>
629 <p>
630 Give the output in an easy-to-parse format for scripts.
631 This is similar to the short output, but will remain stable
632 across git versions and regardless of user configuration. See
633 below for details.
634 </p>
635 </dd>
638 </dt>
641 </dt>
642 <dd>
643 <p>
644 Show untracked files.
645 </p>
646 <div class="paragraph"><p>The mode parameter is optional (defaults to <em>all</em>), and is used to
647 specify the handling of untracked files; when -u is not used, the
651 <li>
652 <p>
654 </p>
655 </li>
656 <li>
657 <p>
659 </p>
660 </li>
661 <li>
662 <p>
664 </p>
667 </li>
668 </ul></div>
669 </dd>
672 </dt>
673 <dd>
674 <p>
677 Using "none" will consider the submodule modified when it either contains
678 untracked or modified files or its HEAD differs from the commit recorded
679 in the superproject and can be used to override any settings of the
680 <em>ignore</em> option in <a href="git-config.html">git-config(1)</a> or <a href="gitmodules.html">gitmodules(5)</a>. When
681 "untracked" is used submodules are not considered dirty when they only
682 contain untracked content (but they are still scanned for modified
683 content). Using "dirty" ignores all changes to the work tree of submodules,
684 only changes to the commits stored in the superproject are shown (this was
686 (and suppresses the output of submodule summaries when the config option
688 </p>
689 </dd>
691 --ignored
692 </dt>
693 <dd>
694 <p>
695 Show ignored files as well.
696 </p>
697 </dd>
699 -z
700 </dt>
701 <dd>
702 <p>
703 Terminate entries with NUL, instead of LF. This implies
705 </p>
706 </dd>
707 </dl></div>
708 </div>
713 The default, long format, is designed to be human readable,
714 verbose and descriptive. Its contents and format are subject to change
715 at any time.</p></div>
716 <div class="paragraph"><p>The paths mentioned in the output, unlike many other git commands, are
717 made relative to the current directory if you are working in a
718 subdirectory (this is on purpose, to help cutting and pasting). See
719 the status.relativePaths config option below.</p></div>
725 </div></div>
726 <div class="paragraph"><p>where <tt>PATH1</tt> is the path in the <tt>HEAD</tt>, and the ` -> PATH2` part is
729 status code.</p></div>
730 <div class="paragraph"><p>The fields (including the <tt>-></tt>) are separated from each other by a
731 single space. If a filename contains whitespace or other nonprintable
732 characters, that field will be quoted in the manner of a C string
733 literal: surrounded by ASCII double quote (34) characters, and with
734 interior special characters backslash-escaped.</p></div>
735 <div class="paragraph"><p>For paths with merge conflicts, <tt>X</tt> and <em>Y</em> show the modification
736 states of each side of the merge. For paths that do not have merge
739 codes can be interpreted as follows:</p></div>
741 <li>
742 <p>
743 ' ' = unmodified
744 </p>
745 </li>
746 <li>
747 <p>
749 </p>
750 </li>
751 <li>
752 <p>
754 </p>
755 </li>
756 <li>
757 <p>
759 </p>
760 </li>
761 <li>
762 <p>
764 </p>
765 </li>
766 <li>
767 <p>
769 </p>
770 </li>
771 <li>
772 <p>
774 </p>
775 </li>
776 </ul></div>
777 <div class="paragraph"><p>Ignored files are not listed, unless <tt>--ignored</tt> option is in effect,
781 <pre><tt>X Y Meaning
782 -------------------------------------------------
783 [MD] not updated
784 M [ MD] updated in index
785 A [ MD] added to index
786 D [ M] deleted from index
787 R [ MD] renamed in index
788 C [ MD] copied in index
789 [MARC] index and work tree matches
790 [ MARC] M work tree changed since index
791 [ MARC] D deleted in work tree
792 -------------------------------------------------
793 D D unmerged, both deleted
794 A U unmerged, added by us
795 U D unmerged, deleted by them
796 U A unmerged, added by them
797 D U unmerged, deleted by us
798 A A unmerged, both added
799 U U unmerged, both modified
800 -------------------------------------------------
801 ? ? untracked
802 ! ! ignored
803 -------------------------------------------------</tt></pre>
804 </div></div>
808 <div class="paragraph"><p>The porcelain format is similar to the short format, but is guaranteed
809 not to change in a backwards-incompatible way between git versions or
810 based on user configuration. This makes it ideal for parsing by scripts.
811 The description of the short format above also describes the porcelain
812 format, with a few exceptions:</p></div>
814 <li>
815 <p>
816 The user’s color.status configuration is not respected; color will
817 always be off.
818 </p>
819 </li>
820 <li>
821 <p>
822 The user’s status.relativePaths configuration is not respected; paths
823 shown will always be relative to the repository root.
824 </p>
825 </li>
826 </ol></div>
827 <div class="paragraph"><p>There is also an alternate -z format recommended for machine parsing. In
828 that format, the status field is the same, but some other things
831 (ASCII 0) follows each filename, replacing space as a field separator
832 and the terminating newline (but a space still separates the status
833 field from the first filename). Third, filenames containing special
834 characters are not specially formatted; no quoting or
835 backslash-escaping is performed. Fourth, there is no branch line.</p></div>
836 </div>
839 <div class="paragraph"><p>The command honors <tt>color.status</tt> (or <tt>status.color</tt> — they
840 mean the same thing and the latter is kept for backward
842 to colorize its output.</p></div>
843 <div class="paragraph"><p>If the config variable <tt>status.relativePaths</tt> is set to false, then all
844 paths shown are relative to the repository root, not to the current
845 directory.</p></div>
846 <div class="paragraph"><p>If <tt>status.submodulesummary</tt> is set to a non zero number or true (identical
847 to -1 or an unlimited number), the submodule summary will be enabled for
848 the long format and a summary of commits for modified submodules will be
849 shown (see --summary-limit option of <a href="git-submodule.html">git-submodule(1)</a>).</p></div>
850 </div>
854 </div>
858 </div>
859 </div>
864 </div>
865 </div>
866 </body>
867 </html>