| blob | 89da6237575d3eaa9f4d9a54d701fdc925e81b8d |
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-add(1) Manual Page
574 </h1>
577 <p>git-add -
578 Add file contents to the index
579 </p>
580 </div>
581 </div>
586 <div class="verseblock-content"><em>git add</em> [-n] [-v] [--force | -f] [--interactive | -i] [--patch | -p]
587 [--edit | -e] [--all | [--update | -u]] [--intent-to-add | -N]
588 [--refresh] [--ignore-errors] [--ignore-missing] [--]
591 </div></div>
592 </div>
596 the working tree, to prepare the content staged for the next commit.
597 It typically adds the current content of existing paths as a whole,
598 but with some options it can also be used to add content with
599 only part of the changes made to the working tree files applied, or
600 remove paths that do not exist in the working tree anymore.</p></div>
601 <div class="paragraph"><p>The "index" holds a snapshot of the content of the working tree, and it
602 is this snapshot that is taken as the contents of the next commit. Thus
603 after making any changes to the working directory, and before running
605 modified files to the index.</p></div>
607 adds the content of the specified file(s) at the time the add command is
608 run; if you want subsequent changes included in the next commit, then
610 <div class="paragraph"><p>The <tt>git status</tt> command can be used to obtain a summary of which
611 files have changes that are staged for the next commit.</p></div>
612 <div class="paragraph"><p>The <tt>git add</tt> command will not add ignored files by default. If any
614 will fail with a list of ignored files. Ignored files reached by
615 directory recursion or filename globbing performed by Git (quote your
618 <div class="paragraph"><p>Please see <a href="git-commit.html">git-commit(1)</a> for alternative ways to add content to a
619 commit.</p></div>
620 </div>
626 </dt>
627 <dd>
628 <p>
630 be given to add all matching files. Also a
633 directory, recursively.
634 </p>
635 </dd>
637 -n
638 </dt>
640 --dry-run
641 </dt>
642 <dd>
643 <p>
644 Don’t actually add the file(s), just show if they exist and/or will
645 be ignored.
646 </p>
647 </dd>
649 -v
650 </dt>
652 --verbose
653 </dt>
654 <dd>
655 <p>
656 Be verbose.
657 </p>
658 </dd>
660 -f
661 </dt>
663 --force
664 </dt>
665 <dd>
666 <p>
667 Allow adding otherwise ignored files.
668 </p>
669 </dd>
671 -i
672 </dt>
674 --interactive
675 </dt>
676 <dd>
677 <p>
678 Add modified contents in the working tree interactively to
679 the index. Optional path arguments may be supplied to limit
680 operation to a subset of the working tree. See “Interactive
681 mode” for details.
682 </p>
683 </dd>
685 -p
686 </dt>
688 --patch
689 </dt>
690 <dd>
691 <p>
692 Interactively choose hunks of patch between the index and the
693 work tree and add them to the index. This gives the user a chance
694 to review the difference before adding modified contents to the
695 index.
696 </p>
700 </dd>
702 -e, --edit
703 </dt>
704 <dd>
705 <p>
706 Open the diff vs. the index in an editor and let the user
707 edit it. After the editor was closed, adjust the hunk headers
708 and apply the patch to the index.
709 </p>
711 apply, or even to modify the contents of lines to be staged. This can be
712 quicker and more flexible than using the interactive hunk selector.
713 However, it is easy to confuse oneself and create a patch that does not
714 apply to the index. See EDITING PATCHES below.</p></div>
715 </dd>
717 -u
718 </dt>
720 --update
721 </dt>
722 <dd>
723 <p>
725 the index rather than the working tree. That means that it
726 will never stage new files, but that it will stage modified
727 new contents of tracked files and that it will remove files
728 from the index if the corresponding files in the working tree
729 have been removed.
730 </p>
732 update all tracked files in the current directory and its
733 subdirectories.</p></div>
734 </dd>
736 -A
737 </dt>
739 --all
740 </dt>
741 <dd>
742 <p>
744 working tree in addition to the index. That means that it
745 will find new files as well as staging modified content and
746 removing files that are no longer in the working tree.
747 </p>
748 </dd>
750 -N
751 </dt>
753 --intent-to-add
754 </dt>
755 <dd>
756 <p>
757 Record only the fact that the path will be added later. An entry
758 for the path is placed in the index with no content. This is
759 useful for, among other things, showing the unstaged content of
761 -a</tt>.
762 </p>
763 </dd>
765 --refresh
766 </dt>
767 <dd>
768 <p>
769 Don’t add the file(s), but only refresh their stat()
770 information in the index.
771 </p>
772 </dd>
774 --ignore-errors
775 </dt>
776 <dd>
777 <p>
778 If some files could not be added because of errors indexing
779 them, do not abort the operation, but continue adding the
780 others. The command shall still exit with non-zero status.
782 true to make this the default behaviour.
783 </p>
784 </dd>
786 --ignore-missing
787 </dt>
788 <dd>
789 <p>
790 This option can only be used together with --dry-run. By using
791 this option the user can check if any of the given files would
792 be ignored, no matter if they are already present in the work
793 tree or not.
794 </p>
795 </dd>
797 --
798 </dt>
799 <dd>
800 <p>
801 This option can be used to separate command-line options from
802 the list of files, (useful when filenames might be mistaken
803 for command-line options).
804 </p>
805 </dd>
806 </dl></div>
807 </div>
810 <div class="paragraph"><p>The optional configuration variable <tt>core.excludesfile</tt> indicates a path to a
811 file containing patterns of file names to exclude from git-add, similar to
812 $GIT_DIR/info/exclude. Patterns in the exclude file are used in addition to
813 those in info/exclude. See <a href="gitrepository-layout.html">gitrepository-layout(5)</a>.</p></div>
814 </div>
818 <li>
819 <p>
821 and its subdirectories:
822 </p>
826 </div></div>
828 example; this lets the command include the files from
830 </li>
831 <li>
832 <p>
833 Considers adding content from all git-*.sh scripts:
834 </p>
838 </div></div>
840 listing the files explicitly), it does not consider
842 </li>
843 </ul></div>
844 </div>
849 interactive command loop.</p></div>
851 gives a prompt "What now> ". In general, when the prompt ends
853 and type return, like this:</p></div>
856 <pre><tt> *** Commands ***
860 </div></div>
861 <div class="paragraph"><p>You also could say <tt>s</tt> or <tt>sta</tt> or <tt>status</tt> above as long as the
862 choice is unique.</p></div>
863 <div class="paragraph"><p>The main command loop has 6 subcommands (plus help and quit).</p></div>
866 status
867 </dt>
868 <dd>
869 <p>
870 This shows the change between HEAD and index (i.e. what will be
872 working tree files (i.e. what you could stage further before
874 looks like this:
875 </p>
878 <pre><tt> staged unstaged path
879 1: binary nothing foo.png
881 </div></div>
883 binary so line count cannot be shown) and there is no
884 difference between indexed copy and the working tree
885 version (if the working tree version were also different,
888 and 35 lines deleted if you commit what is in the index, but
889 working tree file has further modifications (one addition and
890 one deletion).</p></div>
891 </dd>
893 update
894 </dt>
895 <dd>
896 <p>
897 This shows the status information and issues an "Update>>"
899 make more than one selection, concatenated with whitespace or
900 comma. Also you can say ranges. E.g. "2-5 7,9" to choose
902 omitted, all remaining patches are taken. E.g. "7-" to choose
904 </p>
906 like this:</p></div>
909 <pre><tt> staged unstaged path
910 1: binary nothing foo.png
912 </div></div>
914 like this:</p></div>
918 </div></div>
920 contents of working tree files for selected paths in the index.</p></div>
921 </dd>
923 revert
924 </dt>
925 <dd>
926 <p>
928 information for selected paths are reverted to that of the
929 HEAD version. Reverting new paths makes them untracked.
930 </p>
931 </dd>
933 add untracked
934 </dt>
935 <dd>
936 <p>
939 </p>
940 </dd>
942 patch
943 </dt>
944 <dd>
945 <p>
947 After choosing the path, it presents the diff between the index
948 and the working tree file and asks you if you want to stage
949 the change of each hunk. You can select one of the following
950 options and type return:
951 </p>
954 <pre><tt>y - stage this hunk
955 n - do not stage this hunk
956 q - quit; do not stage this hunk nor any of the remaining ones
957 a - stage this hunk and all later hunks in the file
958 d - do not stage this hunk nor any of the later hunks in the file
959 g - select a hunk to go to
960 / - search for a hunk matching the given regex
961 j - leave this hunk undecided, see next undecided hunk
962 J - leave this hunk undecided, see next hunk
963 k - leave this hunk undecided, see previous undecided hunk
964 K - leave this hunk undecided, see previous hunk
965 s - split the current hunk into smaller hunks
966 e - manually edit the current hunk
967 ? - print help</tt></pre>
968 </div></div>
970 that was chosen, the index is updated with the selected hunks.</p></div>
973 </dd>
975 diff
976 </dt>
977 <dd>
978 <p>
979 This lets you review what will be committed (i.e. between
980 HEAD and index).
981 </p>
982 </dd>
983 </dl></div>
984 </div>
987 <div class="paragraph"><p>Invoking <tt>git add -e</tt> or selecting <tt>e</tt> from the interactive hunk
988 selector will open a patch in your editor; after the editor exits, the
989 result is applied to the index. You are free to make arbitrary changes
990 to the patch, but note that some changes may have confusing results, or
991 even result in a patch that cannot be applied. If you want to abort the
992 operation entirely (i.e., stage nothing new in the index), simply delete
993 all lines of the patch. The list below describes some common things you
994 may see in a patch, and which editing operations make sense on them.</p></div>
997 added content
998 </dt>
999 <dd>
1000 <p>
1001 Added content is represented by lines beginning with "+". You can
1002 prevent staging any addition lines by deleting them.
1003 </p>
1004 </dd>
1006 removed content
1007 </dt>
1008 <dd>
1009 <p>
1010 Removed content is represented by lines beginning with "-". You can
1012 </p>
1013 </dd>
1015 modified content
1016 </dt>
1017 <dd>
1018 <p>
1019 Modified content is represented by "-" lines (removing the old content)
1020 followed by "+" lines (adding the replacement content). You can
1022 removing "+" lines. Beware that modifying only half of the pair is
1023 likely to introduce confusing changes to the index.
1024 </p>
1025 </dd>
1026 </dl></div>
1027 <div class="paragraph"><p>There are also more complex operations that can be performed. But beware
1028 that because the patch is applied only to the index and not the working
1029 tree, the working tree will appear to "undo" the change in the index.
1030 For example, introducing a new line into the index that is in neither
1031 the HEAD nor the working tree will stage the new line for commit, but
1032 the line will appear to be reverted in the working tree.</p></div>
1033 <div class="paragraph"><p>Avoid using these constructs, or do so with extreme caution.</p></div>
1036 removing untouched content
1037 </dt>
1038 <dd>
1039 <p>
1040 Content which does not differ between the index and working tree may be
1041 shown on context lines, beginning with a " " (space). You can stage
1042 context lines for removal by converting the space to a "-". The
1043 resulting working tree file will appear to re-add the content.
1044 </p>
1045 </dd>
1047 modifying existing content
1048 </dt>
1049 <dd>
1050 <p>
1051 One can also modify context lines by staging them for removal (by
1053 Similarly, one can modify "+" lines for existing additions or
1054 modifications. In all cases, the new modification will appear reverted
1055 in the working tree.
1056 </p>
1057 </dd>
1059 new content
1060 </dt>
1061 <dd>
1062 <p>
1063 You may also add new content that does not exist in the patch; simply
1064 add new lines, each starting with "+". The addition will appear
1065 reverted in the working tree.
1066 </p>
1067 </dd>
1068 </dl></div>
1069 <div class="paragraph"><p>There are also several operations which should be avoided entirely, as
1070 they will make the patch impossible to apply:</p></div>
1072 <li>
1073 <p>
1075 </p>
1076 </li>
1077 <li>
1078 <p>
1079 deleting context or removal lines
1080 </p>
1081 </li>
1082 <li>
1083 <p>
1084 modifying the contents of context or removal lines
1085 </p>
1086 </li>
1087 </ul></div>
1088 </div>
1097 </div>
1101 </div>
1102 </div>
1107 </div>
1108 </div>
1109 </body>
1110 </html>