| blob | 59c73b28be70f6cd120f42e195ec277e92c7f521 |
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-config(1) Manual Page
407 </h1>
410 <p>git-config -
411 Get and set repository or global options
412 </p>
413 </div>
414 </div>
418 <div class="verseblock-content"><em>git config</em> [<file-option>] [type] [-z|--null] name [value [value_regex]]
423 <em>git config</em> [<file-option>] [type] [-z|--null] --get-regexp name_regex [value_regex]
433 </div></div>
434 </div>
437 <div class="paragraph"><p>You can query/set/replace/unset options with this command. The name is
438 actually the section and the key separated by a dot, and the value will be
439 escaped.</p></div>
440 <div class="paragraph"><p>Multiple lines can be added to an option by using the <em>--add</em> option.
441 If you want to update or unset an option which can occur on multiple
443 existing values that match the regexp are updated or unset. If
445 prepend a single exclamation mark in front (see also <a href="#EXAMPLES">[EXAMPLES]</a>).</p></div>
446 <div class="paragraph"><p>The type specifier can be either <em>--int</em> or <em>--bool</em>, to make
448 convert the value to the canonical form (simple decimal number for int,
451 checks or transformations are performed on the value.</p></div>
452 <div class="paragraph"><p>The file-option can be one of <em>--system</em>, <em>--global</em> or <em>--file</em>
453 which specify where the values will be read from or written to.
454 The default is to assume the config file of the current repository,
455 .git/config unless defined otherwise with GIT_DIR and GIT_CONFIG
459 <li>
460 <p>
461 The config file is invalid,
462 </p>
463 </li>
464 <li>
465 <p>
466 Can not write to the config file,
467 </p>
468 </li>
469 <li>
470 <p>
471 no section was provided,
472 </p>
473 </li>
474 <li>
475 <p>
476 the section or key is invalid,
477 </p>
478 </li>
479 <li>
480 <p>
481 you try to unset an option which does not exist,
482 </p>
483 </li>
484 <li>
485 <p>
486 you try to unset/set an option for which multiple lines match, or
487 </p>
488 </li>
489 <li>
490 <p>
492 </p>
493 </li>
494 </ol></div>
495 </div>
500 --replace-all
501 </dt>
502 <dd>
503 <p>
504 Default behavior is to replace at most one line. This replaces
505 all lines matching the key (and optionally the value_regex).
506 </p>
507 </dd>
509 --add
510 </dt>
511 <dd>
512 <p>
513 Adds a new line to the option without altering any existing
516 </p>
517 </dd>
519 --get
520 </dt>
521 <dd>
522 <p>
523 Get the value for a given key (optionally filtered by a regex
524 matching the value). Returns error code 1 if the key was not
525 found and error code 2 if multiple key values were found.
526 </p>
527 </dd>
529 --get-all
530 </dt>
531 <dd>
532 <p>
533 Like get, but does not fail if the number of values for the key
534 is not exactly one.
535 </p>
536 </dd>
538 --get-regexp
539 </dt>
540 <dd>
541 <p>
542 Like --get-all, but interprets the name as a regular expression.
543 Also outputs the key names.
544 </p>
545 </dd>
547 --global
548 </dt>
549 <dd>
550 <p>
551 For writing options: write to global ~/.gitconfig file rather than
552 the repository .git/config.
553 </p>
555 from all available files.</p></div>
557 </dd>
559 --system
560 </dt>
561 <dd>
562 <p>
563 For writing options: write to system-wide $(prefix)/etc/gitconfig
564 rather than the repository .git/config.
565 </p>
566 <div class="paragraph"><p>For reading options: read only from system-wide $(prefix)/etc/gitconfig
567 rather than from all available files.</p></div>
569 </dd>
571 -f config-file
572 </dt>
574 --file config-file
575 </dt>
576 <dd>
577 <p>
578 Use the given config file instead of the one specified by GIT_CONFIG.
579 </p>
580 </dd>
582 --remove-section
583 </dt>
584 <dd>
585 <p>
586 Remove the given section from the configuration file.
587 </p>
588 </dd>
590 --rename-section
591 </dt>
592 <dd>
593 <p>
594 Rename the given section to a new name.
595 </p>
596 </dd>
598 --unset
599 </dt>
600 <dd>
601 <p>
602 Remove the line matching the key from config file.
603 </p>
604 </dd>
606 --unset-all
607 </dt>
608 <dd>
609 <p>
610 Remove all lines matching the key from config file.
611 </p>
612 </dd>
614 -l
615 </dt>
617 --list
618 </dt>
619 <dd>
620 <p>
621 List all variables set in config file.
622 </p>
623 </dd>
625 --bool
626 </dt>
627 <dd>
628 <p>
630 </p>
631 </dd>
633 --int
634 </dt>
635 <dd>
636 <p>
639 in the config file will cause the value to be multiplied
641 </p>
642 </dd>
644 --bool-or-int
645 </dt>
646 <dd>
647 <p>
649 either --bool or --int, as described above.
650 </p>
651 </dd>
653 --path
654 </dt>
655 <dd>
656 <p>
659 specified user. This option has no effect when setting the
661 command line to let your shell do the expansion).
662 </p>
663 </dd>
665 -z
666 </dt>
668 --null
669 </dt>
670 <dd>
671 <p>
672 For all options that output values and/or keys, always
673 end values with the null character (instead of a
674 newline). Use newline instead as a delimiter between
675 key and value. This allows for secure parsing of the
676 output without getting confused e.g. by values that
677 contain line breaks.
678 </p>
679 </dd>
681 --get-colorbool name [stdout-is-tty]
682 </dt>
683 <dd>
684 <p>
687 "false", and is taken into account when configuration says
689 output of the command itself, and exits with status 0 if color
690 is to be used, or exits with status 1 otherwise.
693 </p>
694 </dd>
696 --get-color name [default]
697 </dt>
698 <dd>
699 <p>
701 output it as the ANSI color escape sequence to the standard
704 </p>
705 </dd>
707 -e
708 </dt>
710 --edit
711 </dt>
712 <dd>
713 <p>
714 Opens an editor to modify the specified config file; either
716 </p>
717 </dd>
718 </dl></div>
719 </div>
722 <div class="paragraph"><p>If not set explicitly with <em>--file</em>, there are three files where
726 $GIT_DIR/config
727 </dt>
728 <dd>
729 <p>
730 Repository specific configuration file. (The filename is
731 of course relative to the repository root, not the working
732 directory.)
733 </p>
734 </dd>
736 ~/.gitconfig
737 </dt>
738 <dd>
739 <p>
740 User-specific configuration file. Also called "global"
741 configuration file.
742 </p>
743 </dd>
745 $(prefix)/etc/gitconfig
746 </dt>
747 <dd>
748 <p>
749 System-wide configuration file.
750 </p>
751 </dd>
752 </dl></div>
753 <div class="paragraph"><p>If no further options are given, all reading options will read all of these
754 files that are available. If the global or the system-wide configuration
755 file are not available they will be ignored. If the repository configuration
757 error code. However, in neither case will an error message be issued.</p></div>
760 and <em>--unset</em>. <strong><em>git config</em> will only ever change one file at a time</strong>.</p></div>
761 <div class="paragraph"><p>You can override these rules either by command line options or by environment
763 to the global or system-wide file respectively. The GIT_CONFIG environment
764 variable has a similar effect, but you can specify any filename you want.</p></div>
765 </div>
770 GIT_CONFIG
771 </dt>
772 <dd>
773 <p>
774 Take the configuration from the given file instead of .git/config.
775 Using the "--global" option forces this to ~/.gitconfig. Using the
776 "--system" option forces this to $(prefix)/etc/gitconfig.
777 </p>
778 </dd>
779 </dl></div>
781 </div>
787 <pre><tt>#
788 # This is the config file, and
789 # a '#' or ';' character indicates
790 # a comment
791 #</tt></pre>
792 </div></div>
795 <pre><tt>; core variables
796 [core]
797 ; Don't trust file modes
798 filemode = false</tt></pre>
799 </div></div>
802 <pre><tt>; Our diff algorithm
803 [diff]
804 external = /usr/local/bin/diff-wrapper
805 renames = true</tt></pre>
806 </div></div>
809 <pre><tt>; Proxy settings
810 [core]
812 gitproxy=default-proxy ; for all the rest</tt></pre>
813 </div></div>
818 </div></div>
819 <div class="paragraph"><p>The hypothetical proxy command entries actually have a postfix to discern
820 what URL they apply to. Here is how to change the entry for kernel.org
825 </div></div>
826 <div class="paragraph"><p>This makes sure that only the key/value pair for kernel.org is replaced.</p></div>
831 </div></div>
832 <div class="paragraph"><p>If you want to delete an entry for a multivar (like core.gitproxy above),
833 you have to provide a regex matching the value of exactly one line.</p></div>
838 </div></div>
843 </div></div>
848 </div></div>
853 </div></div>
854 <div class="paragraph"><p>If you like to live dangerously, you can replace <strong>all</strong> core.gitproxy by a
855 new one with</p></div>
859 </div></div>
860 <div class="paragraph"><p>However, if you really only want to replace the line for the default proxy,
865 </div></div>
866 <div class="paragraph"><p>To actually match only values with an exclamation mark, you have to</p></div>
870 </div></div>
871 <div class="paragraph"><p>To add a new proxy, without altering any of the existing ones, use</p></div>
875 </div></div>
877 script:</p></div>
880 <pre><tt>#!/bin/sh
881 WS=$(git config --get-color color.diff.whitespace "blue reverse")
884 </div></div>
885 </div>
890 is used to store the configuration for that repository, and
893 can be used to store a system-wide default configuration.</p></div>
895 and the porcelains. The variables are divided into sections, wherein
896 the fully qualified variable name of the variable itself is the last
897 dot-separated segment and the section name is everything before the last
898 dot. The variable names are case-insensitive and only alphanumeric
899 characters are allowed. Some variables may appear multiple times.</p></div>
903 blank lines are ignored.</p></div>
905 the name of the section in square brackets and continues until the next
906 section begins. Section names are not case sensitive. Only alphanumeric
908 must belong to some section, which means that there must be a section
909 header before the first setting of a variable.</p></div>
910 <div class="paragraph"><p>Sections can be further divided into subsections. To begin a subsection
911 put its name in double quotes, separated by space from the section name,
912 in the section header, like in the example below:</p></div>
916 </div></div>
917 <div class="paragraph"><p>Subsection names are case sensitive and can contain any characters except
918 newline (doublequote <tt>"</tt> and backslash have to be escaped as <tt>\"</tt> and <tt>\\</tt>,
919 respectively). Section headers cannot span multiple
920 lines. Variables may belong directly to a section or to a given subsection.
923 <div class="paragraph"><p>There is also a case insensitive alternative <tt>[section.subsection]</tt> syntax.
924 In this syntax, subsection names follow the same restrictions as for section
925 names.</p></div>
927 header) are recognized as setting variables, in the form
930 The variable names are case-insensitive and only alphanumeric
932 for a given variable; we say then that variable is multivalued.</p></div>
934 Internal whitespace within a variable value is retained verbatim.</p></div>
935 <div class="paragraph"><p>The values following the equals sign in variable assign are all either
936 a string, an integer, or a boolean. Boolean values may be given as yes/no,
941 You need to enclose variable values in double quotes if you want to
942 preserve leading or trailing whitespace, or if the variable value contains
946 <div class="paragraph"><p>The following escape sequences (beside <tt>\"</tt> and <tt>\\</tt>) are recognized:
949 char sequences are valid.</p></div>
950 <div class="paragraph"><p>Variable values ending in a <tt>\</tt> are continued on the next line in the
951 customary UNIX fashion.</p></div>
956 <pre><tt># Core variables
957 [core]
958 ; Don't trust file modes
959 filemode = false</tt></pre>
960 </div></div>
963 <pre><tt># Our diff algorithm
964 [diff]
965 external = /usr/local/bin/diff-wrapper
966 renames = true</tt></pre>
967 </div></div>
971 remote = origin
972 merge = refs/heads/devel</tt></pre>
973 </div></div>
976 <pre><tt># Proxy settings
977 [core]
979 gitProxy=default-proxy ; for the rest</tt></pre>
980 </div></div>
982 <div class="paragraph"><p>Note that this list is non-comprehensive and not necessarily complete.
983 For command-specific variables, you will find a more detailed description
984 in the appropriate manual page. You will find a description of non-core
985 porcelain configuration variables in the respective porcelain documentation.</p></div>
988 advice.*
989 </dt>
990 <dd>
991 <p>
994 are:
995 </p>
998 pushNonFastForward
999 </dt>
1000 <dd>
1001 <p>
1003 non-fast-forward refs. Default: true.
1004 </p>
1005 </dd>
1007 statusHints
1008 </dt>
1009 <dd>
1010 <p>
1011 Directions on how to stage/unstage/add shown in the
1013 when writing commit messages. Default: true.
1014 </p>
1015 </dd>
1017 commitBeforeMerge
1018 </dt>
1019 <dd>
1020 <p>
1022 merge to avoid overwriting local changes.
1023 Default: true.
1024 </p>
1025 </dd>
1027 resolveConflict
1028 </dt>
1029 <dd>
1030 <p>
1031 Advices shown by various commands when conflicts
1032 prevent the operation from being performed.
1033 Default: true.
1034 </p>
1035 </dd>
1037 implicitIdentity
1038 </dt>
1039 <dd>
1040 <p>
1041 Advice on how to set your identity configuration when
1042 your information is guessed from the system username and
1043 domain name. Default: true.
1044 </p>
1045 </dd>
1047 detachedHead
1048 </dt>
1049 <dd>
1050 <p>
1052 move to the detach HEAD state, to instruct how to create
1053 a local branch after the fact. Default: true.
1054 </p>
1055 </dd>
1056 </dl></div>
1057 </dd>
1059 core.fileMode
1060 </dt>
1061 <dd>
1062 <p>
1063 If false, the executable bit differences between the index and
1064 the working copy are ignored; useful on broken filesystems like FAT.
1066 </p>
1067 <div class="paragraph"><p>The default is true, except <a href="git-clone.html">git-clone(1)</a> or <a href="git-init.html">git-init(1)</a>
1068 will probe and set core.fileMode false if appropriate when the
1069 repository is created.</p></div>
1070 </dd>
1072 core.ignoreCygwinFSTricks
1073 </dt>
1074 <dd>
1075 <p>
1076 This option is only used by Cygwin implementation of Git. If false,
1077 the Cygwin stat() and lstat() functions are used. This may be useful
1078 if your repository consists of a few separate directories joined in
1079 one hierarchy using Cygwin mount. If true, Git uses native Win32 API
1080 whenever it is possible and falls back to Cygwin functions only to
1081 handle symbol links. The native mode is more than twice faster than
1082 normal Cygwin l/stat() functions. True by default, unless core.filemode
1083 is true, in which case ignoreCygwinFSTricks is ignored as Cygwin’s
1084 POSIX emulation is required to support core.filemode.
1085 </p>
1086 </dd>
1088 core.ignorecase
1089 </dt>
1090 <dd>
1091 <p>
1092 If true, this option enables various workarounds to enable
1093 git to work better on filesystems that are not case sensitive,
1094 like FAT. For example, if a directory listing finds
1096 it is really the same file, and continue to remember it as
1097 "Makefile".
1098 </p>
1099 <div class="paragraph"><p>The default is false, except <a href="git-clone.html">git-clone(1)</a> or <a href="git-init.html">git-init(1)</a>
1100 will probe and set core.ignorecase true if appropriate when the repository
1101 is created.</p></div>
1102 </dd>
1104 core.trustctime
1105 </dt>
1106 <dd>
1107 <p>
1108 If false, the ctime differences between the index and the
1109 working copy are ignored; useful when the inode change time
1110 is regularly modified by something outside Git (file system
1111 crawlers and some backup systems).
1113 </p>
1114 </dd>
1116 core.quotepath
1117 </dt>
1118 <dd>
1119 <p>
1122 "unusual" characters in the pathname by enclosing the
1123 pathname in a double-quote pair and with backslashes the
1124 same way strings in C source code are quoted. If this
1125 variable is set to false, the bytes higher than 0x80 are
1126 not quoted but output as verbatim. Note that double
1127 quote, backslash and control characters are always
1129 variable.
1130 </p>
1131 </dd>
1133 core.eol
1134 </dt>
1135 <dd>
1136 <p>
1137 Sets the line ending type to use in the working directory for
1142 conversion.
1143 </p>
1144 </dd>
1146 core.safecrlf
1147 </dt>
1148 <dd>
1149 <p>
1151 end-of-line conversion is active. Git will verify if a command
1152 modifies a file in the work tree either directly or indirectly.
1153 For example, committing a file followed by checking out the
1154 same file should yield the original file in the work tree. If
1155 this is not the case for the current setting of
1157 be set to "warn", in which case git will only warn about an
1158 irreversible conversion but continue the operation.
1159 </p>
1161 When it is enabled, git will convert CRLF to LF during commit and LF to
1162 CRLF during checkout. A file that contains a mixture of LF and
1163 CRLF before the commit cannot be recreated by git. For text
1164 files this is the right thing to do: it corrects line endings
1165 such that we have only LF line endings in the repository.
1166 But for binary files that are accidentally classified as text the
1167 conversion can corrupt data.</p></div>
1169 setting the conversion type explicitly in .gitattributes. Right
1170 after committing you still have the original file in your work
1171 tree and this file is not yet corrupted. You can explicitly tell
1172 git that this file is binary and git will handle the file
1173 appropriately.</p></div>
1175 mixed line endings and the undesired effect of corrupting binary
1176 files cannot be distinguished. In both cases CRLFs are removed
1177 in an irreversible way. For text files this is the right thing
1178 to do because CRLFs are line endings, while for binary files
1179 converting CRLFs corrupts data.</p></div>
1180 <div class="paragraph"><p>Note, this safety check does not mean that a checkout will generate a
1181 file identical to the original file for a different setting of
1189 mechanism.</p></div>
1190 </dd>
1192 core.autocrlf
1193 </dt>
1194 <dd>
1195 <p>
1196 Setting this variable to "true" is almost the same as setting
1198 files are not guaranteed to be normalized: files that contain
1201 working directory even though the repository does not have
1203 in which case no output conversion is performed.
1204 </p>
1205 </dd>
1207 core.symlinks
1208 </dt>
1209 <dd>
1210 <p>
1211 If false, symbolic links are checked out as small plain files that
1214 file. Useful on filesystems like FAT that do not support
1215 symbolic links.
1216 </p>
1217 <div class="paragraph"><p>The default is true, except <a href="git-clone.html">git-clone(1)</a> or <a href="git-init.html">git-init(1)</a>
1218 will probe and set core.symlinks false if appropriate when the repository
1219 is created.</p></div>
1220 </dd>
1222 core.gitProxy
1223 </dt>
1224 <dd>
1225 <p>
1227 of establishing direct connection to the remote server when
1228 using the git protocol for fetching. If the variable value is
1229 in the "COMMAND for DOMAIN" format, the command is applied only
1230 on hostnames ending with the specified domain string. This variable
1231 may be set multiple times and is matched in the given order;
1232 the first match wins.
1233 </p>
1234 <div class="paragraph"><p>Can be overridden by the <em>GIT_PROXY_COMMAND</em> environment variable
1235 (which always applies universally, without the special "for"
1236 handling).</p></div>
1238 specify that no proxy be used for a given domain pattern.
1239 This is useful for excluding servers inside a firewall from
1240 proxy use, while defaulting to a common proxy for external domains.</p></div>
1241 </dd>
1243 core.ignoreStat
1244 </dt>
1245 <dd>
1246 <p>
1247 If true, commands which modify both the working tree and the index
1248 will mark the updated paths with the "assume unchanged" bit in the
1249 index. These marked files are then assumed to stay unchanged in the
1250 working copy, until you mark them otherwise manually - Git will not
1251 detect the file changes by lstat() calls. This is useful on systems
1252 where those are very slow, such as Microsoft Windows.
1254 False by default.
1255 </p>
1256 </dd>
1258 core.preferSymlinkRefs
1259 </dt>
1260 <dd>
1261 <p>
1262 Instead of the default "symref" format for HEAD
1263 and other symbolic reference files, use symbolic links.
1264 This is sometimes needed to work with old scripts that
1265 expect HEAD to be a symbolic link.
1266 </p>
1267 </dd>
1269 core.bare
1270 </dt>
1271 <dd>
1272 <p>
1274 working directory associated with it. If this is the case a
1275 number of commands that require a working directory will be
1276 disabled, such as <a href="git-add.html">git-add(1)</a> or <a href="git-merge.html">git-merge(1)</a>.
1277 </p>
1278 <div class="paragraph"><p>This setting is automatically guessed by <a href="git-clone.html">git-clone(1)</a> or
1280 repository that ends in "/.git" is assumed to be not bare (bare =
1281 false), while all other repositories are assumed to be bare (bare
1282 = true).</p></div>
1283 </dd>
1285 core.worktree
1286 </dt>
1287 <dd>
1288 <p>
1289 Set the path to the root of the working tree.
1290 This can be overridden by the GIT_WORK_TREE environment
1292 The value can be an absolute path or relative to the path to
1293 the .git directory, which is either specified by --git-dir
1294 or GIT_DIR, or automatically discovered.
1295 If --git-dir or GIT_DIR is specified but none of
1296 --work-tree, GIT_WORK_TREE and core.worktree is specified,
1297 the current working directory is regarded as the top level
1298 of your working tree.
1299 </p>
1301 file in a ".git" subdirectory of a directory and its value differs
1302 from the latter directory (e.g. "/path/to/.git/config" has
1303 core.worktree set to "/different/path"), which is most likely a
1304 misconfiguration. Running git commands in the "/path/to" directory will
1305 still use "/different/path" as the root of the work tree and can cause
1306 confusion unless you know what you are doing (e.g. you are creating a
1307 read-only snapshot of the same index to a location different from the
1309 </dd>
1311 core.logAllRefUpdates
1312 </dt>
1313 <dd>
1314 <p>
1316 "$GIT_DIR/logs/<ref>", by appending the new and old
1317 SHA1, the date/time and the reason of the update, but
1318 only when the file exists. If this configuration
1319 variable is set to true, missing "$GIT_DIR/logs/<ref>"
1320 file is automatically created for branch heads.
1321 </p>
1325 a working directory associated with it, and false by
1326 default in a bare repository.</p></div>
1327 </dd>
1329 core.repositoryFormatVersion
1330 </dt>
1331 <dd>
1332 <p>
1333 Internal variable identifying the repository format and layout
1334 version.
1335 </p>
1336 </dd>
1338 core.sharedRepository
1339 </dt>
1340 <dd>
1341 <p>
1343 several users in a group (making sure all the files and objects are
1345 repository will be readable by all users, additionally to being
1349 user’s umask value (whereas the other options will only override
1351 the repo read/write-able for the owner and group, but inaccessible to
1353 repository that is group-readable but not group-writable.
1355 </p>
1356 </dd>
1358 core.warnAmbiguousRefs
1359 </dt>
1360 <dd>
1361 <p>
1362 If true, git will warn you if the ref name you passed it is ambiguous
1363 and might match multiple refs in the .git/refs/ tree. True by default.
1364 </p>
1365 </dd>
1367 core.compression
1368 </dt>
1369 <dd>
1370 <p>
1374 If set, this provides a default to other compression variables,
1376 </p>
1377 </dd>
1379 core.loosecompression
1380 </dt>
1381 <dd>
1382 <p>
1386 slowest. If not set, defaults to core.compression. If that is
1387 not set, defaults to 1 (best speed).
1388 </p>
1389 </dd>
1391 core.packedGitWindowSize
1392 </dt>
1393 <dd>
1394 <p>
1395 Number of bytes of a pack file to map into memory in a
1396 single mapping operation. Larger window sizes may allow
1397 your system to process a smaller number of large pack files
1398 more quickly. Smaller window sizes will negatively affect
1399 performance due to increased calls to the operating system’s
1400 memory manager, but may improve performance when accessing
1401 a large number of large pack files.
1402 </p>
1405 be reasonable for all users/operating systems. You probably do
1406 not need to adjust this value.</p></div>
1407 <div class="paragraph"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1408 </dd>
1410 core.packedGitLimit
1411 </dt>
1412 <dd>
1413 <p>
1414 Maximum number of bytes to map simultaneously into memory
1415 from pack files. If Git needs to access more than this many
1416 bytes at once to complete an operation it will unmap existing
1417 regions to reclaim virtual address space within the process.
1418 </p>
1419 <div class="paragraph"><p>Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms.
1420 This should be reasonable for all users/operating systems, except on
1421 the largest projects. You probably do not need to adjust this value.</p></div>
1422 <div class="paragraph"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1423 </dd>
1425 core.deltaBaseCacheLimit
1426 </dt>
1427 <dd>
1428 <p>
1429 Maximum number of bytes to reserve for caching base objects
1430 that may be referenced by multiple deltified objects. By storing the
1431 entire decompressed base objects in a cache Git is able
1432 to avoid unpacking and decompressing frequently used base
1433 objects multiple times.
1434 </p>
1436 for all users/operating systems, except on the largest projects.
1437 You probably do not need to adjust this value.</p></div>
1438 <div class="paragraph"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1439 </dd>
1441 core.bigFileThreshold
1442 </dt>
1443 <dd>
1444 <p>
1445 Files larger than this size are stored deflated, without
1446 attempting delta compression. Storing large files without
1447 delta compression avoids excessive memory usage, at the
1448 slight expense of increased disk usage.
1449 </p>
1451 for most projects as source code and other text files can still
1453 <div class="paragraph"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1454 </dd>
1456 core.excludesfile
1457 </dt>
1458 <dd>
1459 <p>
1462 of files which are not meant to be tracked. "~/" is expanded
1465 </p>
1466 </dd>
1468 core.askpass
1469 </dt>
1470 <dd>
1471 <p>
1472 Some commands (e.g. svn and http interfaces) that interactively
1473 ask for a password can be told to use an external program given
1475 environment variable. If not set, fall back to the value of the
1477 prompt. The external program shall be given a suitable prompt as
1478 command line argument and write the password on its STDOUT.
1479 </p>
1480 </dd>
1482 core.attributesfile
1483 </dt>
1484 <dd>
1485 <p>
1490 </p>
1491 </dd>
1493 core.editor
1494 </dt>
1495 <dd>
1496 <p>
1498 messages by launching an editor uses the value of this
1499 variable when it is set, and the environment variable
1501 </p>
1502 </dd>
1504 core.pager
1505 </dt>
1506 <dd>
1507 <p>
1508 The command that git will use to paginate output. Can
1512 pager. One can change these settings by setting the
1514 these settings can be overridden on a project or
1517 environment variable behaviour above, so if you want
1518 to override git’s default settings this way, you need
1519 to be explicit. For example, to disable the S option
1522 shell by git, which will translate the final command to
1524 </p>
1525 </dd>
1527 core.whitespace
1528 </dt>
1529 <dd>
1530 <p>
1531 A comma separated list of common whitespace problems to
1536 </p>
1538 <li>
1539 <p>
1541 as an error (enabled by default).
1542 </p>
1543 </li>
1544 <li>
1545 <p>
1547 before a tab character in the initial indent part of the line as an
1548 error (enabled by default).
1549 </p>
1550 </li>
1551 <li>
1552 <p>
1554 space characters as an error (not enabled by default).
1555 </p>
1556 </li>
1557 <li>
1558 <p>
1560 the line as an error (not enabled by default).
1561 </p>
1562 </li>
1563 <li>
1564 <p>
1566 (enabled by default).
1567 </p>
1568 </li>
1569 <li>
1570 <p>
1573 </p>
1574 </li>
1575 <li>
1576 <p>
1579 does not trigger if the character before such a carriage-return
1580 is not a whitespace (not enabled by default).
1581 </p>
1582 </li>
1583 <li>
1584 <p>
1588 </p>
1589 </li>
1590 </ul></div>
1591 </dd>
1593 core.fsyncobjectfiles
1594 </dt>
1595 <dd>
1596 <p>
1598 </p>
1600 data writes properly, but can be useful for filesystems that do not use
1601 journalling (traditional UNIX filesystems) or that only journal metadata
1603 </dd>
1605 core.preloadindex
1606 </dt>
1607 <dd>
1608 <p>
1610 </p>
1611 <div class="paragraph"><p>This can speed up operations like <em>git diff</em> and <em>git status</em> especially
1612 on filesystems like NFS that have weak caching semantics and thus
1614 index comparison to the filesystem data in parallel, allowing
1616 </dd>
1618 core.createObject
1619 </dt>
1620 <dd>
1621 <p>
1623 a delete of the source are used to make sure that object creation
1624 will not overwrite existing objects.
1625 </p>
1626 <div class="paragraph"><p>On some file system/operating system combinations, this is unreliable.
1628 check that makes sure that existing object files will not get overwritten.</p></div>
1629 </dd>
1631 core.notesRef
1632 </dt>
1633 <dd>
1634 <p>
1635 When showing commit messages, also show notes which are stored in
1636 the given ref. The ref must be fully qualified. If the given
1637 ref does not exist, it is not an error but means that no
1638 notes should be printed.
1639 </p>
1640 <div class="paragraph"><p>This setting defaults to "refs/notes/commits", and it can be overridden by
1641 the <em>GIT_NOTES_REF</em> environment variable. See <a href="git-notes.html">git-notes(1)</a>.</p></div>
1642 </dd>
1644 core.sparseCheckout
1645 </dt>
1646 <dd>
1647 <p>
1650 </p>
1651 </dd>
1653 core.abbrev
1654 </dt>
1655 <dd>
1656 <p>
1657 Set the length object names are abbreviated to. If unspecified,
1658 many commands abbreviate to 7 hexdigits, which may not be enough
1659 for abbreviated object names to stay unique for sufficiently long
1660 time.
1661 </p>
1662 </dd>
1664 add.ignore-errors
1665 </dt>
1667 add.ignoreErrors
1668 </dt>
1669 <dd>
1670 <p>
1675 convention for configuration variables. Newer versions of git
1677 </p>
1678 </dd>
1680 alias.*
1681 </dt>
1682 <dd>
1683 <p>
1685 after defining "alias.last = cat-file commit HEAD", the invocation
1687 confusion and troubles with script usage, aliases that
1688 hide existing git commands are ignored. Arguments are split by
1689 spaces, the usual shell quoting and escaping is supported.
1690 quote pair and a backslash can be used to quote them.
1691 </p>
1693 it will be treated as a shell command. For example, defining
1694 "alias.new = !gitk --all --not ORIG_HEAD", the invocation
1695 "git new" is equivalent to running the shell command
1696 "gitk --all --not ORIG_HEAD". Note that shell commands will be
1697 executed from the top-level directory of a repository, which may
1698 not necessarily be the current directory.
1700 from the original current directory. See <a href="git-rev-parse.html">git-rev-parse(1)</a>.</p></div>
1701 </dd>
1703 am.keepcr
1704 </dt>
1705 <dd>
1706 <p>
1707 If true, git-am will call git-mailsplit for patches in mbox format
1712 </p>
1713 </dd>
1715 apply.ignorewhitespace
1716 </dt>
1717 <dd>
1718 <p>
1721 option.
1723 respect all whitespace differences.
1725 </p>
1726 </dd>
1728 apply.whitespace
1729 </dt>
1730 <dd>
1731 <p>
1734 </p>
1735 </dd>
1737 branch.autosetupmerge
1738 </dt>
1739 <dd>
1740 <p>
1743 starting point branch. Note that even if this option is not set,
1747 starting point is a remote-tracking branch; <tt>always</tt> —  automatic setup is done when the starting point is either a
1748 local branch or remote-tracking
1749 branch. This option defaults to true.
1750 </p>
1751 </dd>
1753 branch.autosetuprebase
1754 </dt>
1755 <dd>
1756 <p>
1758 that tracks another branch, this variable tells git to set
1759 up pull to rebase instead of merge (see "branch.<name>.rebase").
1762 other local branches.
1764 remote-tracking branches.
1766 branches.
1767 See "branch.autosetupmerge" for details on how to set up a
1768 branch to track another branch.
1769 This option defaults to never.
1770 </p>
1771 </dd>
1774 </dt>
1775 <dd>
1776 <p>
1780 </p>
1781 </dd>
1784 </dt>
1785 <dd>
1786 <p>
1791 refspec to be marked for merging in FETCH_HEAD. The value is
1792 handled like the remote part of a refspec, and must match a
1793 ref which is fetched from the remote given by
1794 "branch.<name>.remote".
1798 Specify multiple values to get an octopus merge.
1800 another branch in the local repository, you can point
1803 </p>
1804 </dd>
1807 </dt>
1808 <dd>
1809 <p>
1812 option values containing whitespace characters are currently not
1813 supported.
1814 </p>
1815 </dd>
1818 </dt>
1819 <dd>
1820 <p>
1822 instead of merging the default branch from the default remote when
1823 "git pull" is run.
1826 for details).
1827 </p>
1828 </dd>
1831 </dt>
1832 <dd>
1833 <p>
1834 Specify the command to invoke the specified browser. The
1835 specified command is evaluated in shell with the URLs passed
1837 </p>
1838 </dd>
1841 </dt>
1842 <dd>
1843 <p>
1844 Override the path for the given tool that may be used to
1847 </p>
1848 </dd>
1850 clean.requireForce
1851 </dt>
1852 <dd>
1853 <p>
1854 A boolean to make git-clean do nothing unless given -f
1855 or -n. Defaults to true.
1856 </p>
1857 </dd>
1859 color.branch
1860 </dt>
1861 <dd>
1862 <p>
1863 A boolean to enable/disable color in the output of
1865 <tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt> (or <tt>true</tt>), in which case colors are used
1866 only when the output is to a terminal. Defaults to false.
1867 </p>
1868 </dd>
1871 </dt>
1872 <dd>
1873 <p>
1877 refs).
1878 </p>
1879 <div class="paragraph"><p>The value for these configuration variables is a list of colors (at most
1880 two) and attributes (at most one), separated by spaces. The colors
1881 accepted are <tt>normal</tt>, <tt>black</tt>, <tt>red</tt>, <tt>green</tt>, <tt>yellow</tt>, <tt>blue</tt>,
1882 <tt>magenta</tt>, <tt>cyan</tt> and <tt>white</tt>; the attributes are <tt>bold</tt>, <tt>dim</tt>, <tt>ul</tt>,
1884 second is the background. The position of the attribute, if any,
1886 </dd>
1888 color.diff
1889 </dt>
1890 <dd>
1891 <p>
1892 Whether to use ANSI escape sequences to add color to patches.
1894 <a href="git-log.html">git-log(1)</a>, and <a href="git-show.html">git-show(1)</a> will use color
1896 commands will only use color when output is to the terminal.
1897 Defaults to false.
1898 </p>
1899 <div class="paragraph"><p>This does not affect <a href="git-format-patch.html">git-format-patch(1)</a> nor the
1902 </dd>
1905 </dt>
1906 <dd>
1907 <p>
1909 which part of the patch to use the specified color, and is one
1913 (highlighting whitespace errors). The values of these variables may be
1915 </p>
1916 </dd>
1919 </dt>
1920 <dd>
1921 <p>
1923 of <tt>branch</tt>, <tt>remoteBranch</tt>, <tt>tag</tt>, <tt>stash</tt> or <tt>HEAD</tt> for local
1924 branches, remote-tracking branches, tags, stash and HEAD, respectively.
1925 </p>
1926 </dd>
1928 color.grep
1929 </dt>
1930 <dd>
1931 <p>
1935 </p>
1936 </dd>
1939 </dt>
1940 <dd>
1941 <p>
1943 part of the line to use the specified color, and is one of
1944 </p>
1948 </dt>
1949 <dd>
1950 <p>
1952 </p>
1953 </dd>
1956 </dt>
1957 <dd>
1958 <p>
1960 </p>
1961 </dd>
1964 </dt>
1965 <dd>
1966 <p>
1968 </p>
1969 </dd>
1972 </dt>
1973 <dd>
1974 <p>
1976 </p>
1977 </dd>
1980 </dt>
1981 <dd>
1982 <p>
1983 matching text
1984 </p>
1985 </dd>
1988 </dt>
1989 <dd>
1990 <p>
1991 non-matching text in selected lines
1992 </p>
1993 </dd>
1996 </dt>
1997 <dd>
1998 <p>
2001 </p>
2002 </dd>
2003 </dl></div>
2004 <div class="paragraph"><p>The values of these variables may be specified as in color.branch.<slot>.</p></div>
2005 </dd>
2007 color.interactive
2008 </dt>
2009 <dd>
2010 <p>
2012 and displays (such as those used by "git-add --interactive").
2014 colors only when the output is to the terminal. Defaults to false.
2015 </p>
2016 </dd>
2019 </dt>
2020 <dd>
2021 <p>
2023 output. <tt><slot></tt> may be <tt>prompt</tt>, <tt>header</tt>, <tt>help</tt> or <tt>error</tt>, for
2024 four distinct types of normal output from interactive
2025 commands. The values of these variables may be specified as
2027 </p>
2028 </dd>
2030 color.pager
2031 </dt>
2032 <dd>
2033 <p>
2034 A boolean to enable/disable colored output when the pager is in
2035 use (default is true).
2036 </p>
2037 </dd>
2039 color.showbranch
2040 </dt>
2041 <dd>
2042 <p>
2043 A boolean to enable/disable color in the output of
2045 <tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt> (or <tt>true</tt>), in which case colors are used
2046 only when the output is to a terminal. Defaults to false.
2047 </p>
2048 </dd>
2050 color.status
2051 </dt>
2052 <dd>
2053 <p>
2054 A boolean to enable/disable color in the output of
2056 <tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt> (or <tt>true</tt>), in which case colors are used
2057 only when the output is to a terminal. Defaults to false.
2058 </p>
2059 </dd>
2062 </dt>
2063 <dd>
2064 <p>
2072 to red). The values of these variables may be specified as in
2074 </p>
2075 </dd>
2077 color.ui
2078 </dt>
2079 <dd>
2080 <p>
2081 This variable determines the default value for variables such
2083 per command family. Its scope will expand as more commands learn
2090 </p>
2091 </dd>
2093 commit.status
2094 </dt>
2095 <dd>
2096 <p>
2097 A boolean to enable/disable inclusion of status information in the
2098 commit message template when using an editor to prepare the commit
2099 message. Defaults to true.
2100 </p>
2101 </dd>
2103 commit.template
2104 </dt>
2105 <dd>
2106 <p>
2107 Specify a file to use as the template for new commit messages.
2109 specified user’s home directory.
2110 </p>
2111 </dd>
2113 diff.autorefreshindex
2114 </dt>
2115 <dd>
2116 <p>
2118 files, do not consider stat-only change as changed.
2120 update the cached stat information for paths whose
2121 contents in the work tree match the contents in the
2122 index. This option defaults to true. Note that this
2125 </p>
2126 </dd>
2128 diff.dirstat
2129 </dt>
2130 <dd>
2131 <p>
2134 and friends. The defaults can be overridden on the command line
2137 The following parameters are available:
2138 </p>
2142 </dt>
2143 <dd>
2144 <p>
2145 Compute the dirstat numbers by counting the lines that have been
2146 removed from the source, or added to the destination. This ignores
2147 the amount of pure code movements within a file. In other words,
2148 rearranging lines in a file is not counted as much as other changes.
2149 This is the default behavior when no parameter is given.
2150 </p>
2151 </dd>
2154 </dt>
2155 <dd>
2156 <p>
2157 Compute the dirstat numbers by doing the regular line-based diff
2158 analysis, and summing the removed/added line counts. (For binary
2159 files, count 64-byte chunks instead, since binary files have no
2162 lines within a file as much as other changes. The resulting output
2164 </p>
2165 </dd>
2168 </dt>
2169 <dd>
2170 <p>
2171 Compute the dirstat numbers by counting the number of files changed.
2172 Each changed file counts equally in the dirstat analysis. This is
2174 not have to look at the file contents at all.
2175 </p>
2176 </dd>
2179 </dt>
2180 <dd>
2181 <p>
2182 Count changes in a child directory for the parent directory as well.
2184 reported may exceed 100%. The default (non-cumulative) behavior can
2186 </p>
2187 </dd>
2190 </dt>
2191 <dd>
2192 <p>
2193 An integer parameter specifies a cut-off percent (3% by default).
2194 Directories contributing less than this percentage of the changes
2195 are not shown in the output.
2196 </p>
2197 </dd>
2198 </dl></div>
2200 directories with less than 10% of the total amount of changed files,
2201 and accumulating child directory counts in the parent directories:
2203 </dd>
2205 diff.external
2206 </dt>
2207 <dd>
2208 <p>
2209 If this config variable is set, diff generation is not
2210 performed using the internal diff machinery, but using the
2212 environment variable. The command is called with parameters
2214 you want to use an external diff program only on a subset of
2216 </p>
2217 </dd>
2219 diff.ignoreSubmodules
2220 </dt>
2221 <dd>
2222 <p>
2223 Sets the default value of --ignore-submodules. Note that this
2226 this setting when reporting uncommitted changes.
2227 </p>
2228 </dd>
2230 diff.mnemonicprefix
2231 </dt>
2232 <dd>
2233 <p>
2236 this configuration is in effect, reverse diff output also swaps
2237 the order of the prefixes:
2238 </p>
2242 </dt>
2243 <dd>
2244 <p>
2245 compares the (i)ndex and the (w)ork tree;
2246 </p>
2247 </dd>
2250 </dt>
2251 <dd>
2252 <p>
2253 compares a (c)ommit and the (w)ork tree;
2254 </p>
2255 </dd>
2258 </dt>
2259 <dd>
2260 <p>
2261 compares a (c)ommit and the (i)ndex;
2262 </p>
2263 </dd>
2266 </dt>
2267 <dd>
2268 <p>
2269 compares an (o)bject and a (w)ork tree entity;
2270 </p>
2271 </dd>
2274 </dt>
2275 <dd>
2276 <p>
2278 </p>
2279 </dd>
2280 </dl></div>
2281 </dd>
2283 diff.noprefix
2284 </dt>
2285 <dd>
2286 <p>
2288 </p>
2289 </dd>
2291 diff.renameLimit
2292 </dt>
2293 <dd>
2294 <p>
2295 The number of files to consider when performing the copy/rename
2297 </p>
2298 </dd>
2300 diff.renames
2301 </dt>
2302 <dd>
2303 <p>
2304 Tells git to detect renames. If set to any boolean value, it
2305 will enable basic rename detection. If set to "copies" or
2306 "copy", it will detect copies, as well.
2307 </p>
2308 </dd>
2310 diff.suppressBlankEmpty
2311 </dt>
2312 <dd>
2313 <p>
2314 A boolean to inhibit the standard behavior of printing a space
2315 before each empty output line. Defaults to false.
2316 </p>
2317 </dd>
2320 </dt>
2321 <dd>
2322 <p>
2324 for details.
2325 </p>
2326 </dd>
2329 </dt>
2330 <dd>
2331 <p>
2332 The regular expression that the diff driver should use to
2333 recognize the hunk header. A built-in pattern may also be used.
2335 </p>
2336 </dd>
2339 </dt>
2340 <dd>
2341 <p>
2342 Set this option to true to make the diff driver treat files as
2344 </p>
2345 </dd>
2348 </dt>
2349 <dd>
2350 <p>
2351 The command that the diff driver should call to generate the
2352 text-converted version of a file. The result of the
2353 conversion is used to generate a human-readable diff. See
2355 </p>
2356 </dd>
2359 </dt>
2360 <dd>
2361 <p>
2362 The regular expression that the diff driver should use to
2364 details.
2365 </p>
2366 </dd>
2369 </dt>
2370 <dd>
2371 <p>
2372 Set this option to true to make the diff driver cache the text
2374 </p>
2375 </dd>
2377 diff.tool
2378 </dt>
2379 <dd>
2380 <p>
2384 "kompare". Any other value is treated as a custom diff tool,
2386 option.
2387 </p>
2388 </dd>
2391 </dt>
2392 <dd>
2393 <p>
2394 Override the path for the given tool. This is useful in case
2395 your tool is not in the PATH.
2396 </p>
2397 </dd>
2400 </dt>
2401 <dd>
2402 <p>
2403 Specify the command to invoke the specified diff tool.
2404 The specified command is evaluated in shell with the following
2407 is set to the name of the temporary file containing the contents
2408 of the diff post-image.
2409 </p>
2410 </dd>
2412 difftool.prompt
2413 </dt>
2414 <dd>
2415 <p>
2416 Prompt before each invocation of the diff tool.
2417 </p>
2418 </dd>
2420 diff.wordRegex
2421 </dt>
2422 <dd>
2423 <p>
2424 A POSIX Extended Regular Expression used to determine what is a "word"
2425 when performing word-by-word difference calculations. Character
2426 sequences that match the regular expression are "words", all other
2428 </p>
2429 </dd>
2431 fetch.recurseSubmodules
2432 </dt>
2433 <dd>
2434 <p>
2436 Setting it to a boolean changes the behavior of fetch and pull to
2437 unconditionally recurse into submodules when set to true or to not
2439 value), fetch and pull will only recurse into a populated submodule
2440 when its superproject retrieves a commit that updates the submodule’s
2441 reference.
2442 </p>
2443 </dd>
2445 fetch.unpackLimit
2446 </dt>
2447 <dd>
2448 <p>
2449 If the number of objects fetched over the git native
2450 transfer is below this
2451 limit, then the objects will be unpacked into loose object
2452 files. However if the number of received objects equals or
2453 exceeds this limit then the received pack will be stored as
2454 a pack, after adding any missing delta bases. Storing the
2455 pack from a push can make the push operation complete faster,
2456 especially on slow filesystems. If not set, the value of
2458 </p>
2459 </dd>
2461 format.attach
2462 </dt>
2463 <dd>
2464 <p>
2465 Enable multipart/mixed attachments as the default for
2467 which will enable attachments as the default and set the
2468 value as the boundary. See the --attach option in
2470 </p>
2471 </dd>
2473 format.numbered
2474 </dt>
2475 <dd>
2476 <p>
2477 A boolean which can enable or disable sequence numbers in patch
2478 subjects. It defaults to "auto" which enables it only if there
2479 is more than one patch. It can be enabled or disabled for all
2482 </p>
2483 </dd>
2485 format.headers
2486 </dt>
2487 <dd>
2488 <p>
2489 Additional email headers to include in a patch to be submitted
2491 </p>
2492 </dd>
2494 format.to
2495 </dt>
2497 format.cc
2498 </dt>
2499 <dd>
2500 <p>
2501 Additional recipients to include in a patch to be submitted
2502 by mail. See the --to and --cc options in
2504 </p>
2505 </dd>
2507 format.subjectprefix
2508 </dt>
2509 <dd>
2510 <p>
2512 subject prefix. Use this variable to change that prefix.
2513 </p>
2514 </dd>
2516 format.signature
2517 </dt>
2518 <dd>
2519 <p>
2520 The default for format-patch is to output a signature containing
2521 the git version number. Use this variable to change that default.
2522 Set this variable to the empty string ("") to suppress
2523 signature generation.
2524 </p>
2525 </dd>
2527 format.suffix
2528 </dt>
2529 <dd>
2530 <p>
2531 The default for format-patch is to output files with the suffix
2533 include the dot if you want it).
2534 </p>
2535 </dd>
2537 format.pretty
2538 </dt>
2539 <dd>
2540 <p>
2541 The default pretty format for log/show/whatchanged command,
2544 </p>
2545 </dd>
2547 format.thread
2548 </dt>
2549 <dd>
2550 <p>
2553 makes every mail a reply to the head of the series,
2554 where the head is chosen from the cover letter, the
2558 value disables threading.
2559 </p>
2560 </dd>
2562 format.signoff
2563 </dt>
2564 <dd>
2565 <p>
2568 patch should be a conscious act and means that you certify you have
2569 the rights to submit this work under the same open source license.
2571 </p>
2572 </dd>
2575 </dt>
2576 <dd>
2577 <p>
2578 The command which is used to convert the content of a worktree
2580 details.
2581 </p>
2582 </dd>
2585 </dt>
2586 <dd>
2587 <p>
2588 The command which is used to convert the content of a blob
2589 object to a worktree file upon checkout. See
2591 </p>
2592 </dd>
2594 gc.aggressiveWindow
2595 </dt>
2596 <dd>
2597 <p>
2598 The window size parameter used in the delta compression
2600 to 250.
2601 </p>
2602 </dd>
2604 gc.auto
2605 </dt>
2606 <dd>
2607 <p>
2608 When there are approximately more than this many loose
2610 Some Porcelain commands use this command to perform a
2611 light-weight garbage collection from time to time. The
2613 </p>
2614 </dd>
2616 gc.autopacklimit
2617 </dt>
2618 <dd>
2619 <p>
2620 When there are more than this many packs that are not
2622 --auto</tt> consolidates them into one larger pack. The
2624 </p>
2625 </dd>
2627 gc.packrefs
2628 </dt>
2629 <dd>
2630 <p>
2632 unclonable by Git versions prior to 1.5.1.2 over dumb
2633 transports such as HTTP. This variable determines whether
2635 to enable it within all non-bare repos or it can be set to a
2637 </p>
2638 </dd>
2640 gc.pruneexpire
2641 </dt>
2642 <dd>
2643 <p>
2645 Override the grace period with this config variable. The value
2646 "now" may be used to disable this grace period and always prune
2647 unreachable objects immediately.
2648 </p>
2649 </dd>
2651 gc.reflogexpire
2652 </dt>
2655 </dt>
2656 <dd>
2657 <p>
2660 "refs/stash") in the middle the setting applies only to
2662 </p>
2663 </dd>
2665 gc.reflogexpireunreachable
2666 </dt>
2669 </dt>
2670 <dd>
2671 <p>
2673 this time and are not reachable from the current tip;
2675 in the middle, the setting applies only to the refs that
2677 </p>
2678 </dd>
2680 gc.rerereresolved
2681 </dt>
2682 <dd>
2683 <p>
2684 Records of conflicted merge you resolved earlier are
2687 </p>
2688 </dd>
2690 gc.rerereunresolved
2691 </dt>
2692 <dd>
2693 <p>
2694 Records of conflicted merge you have not resolved are
2697 </p>
2698 </dd>
2700 gitcvs.commitmsgannotation
2701 </dt>
2702 <dd>
2703 <p>
2704 Append this string to each commit message. Set to empty string
2705 to disable this feature. Defaults to "via git-CVS emulator".
2706 </p>
2707 </dd>
2709 gitcvs.enabled
2710 </dt>
2711 <dd>
2712 <p>
2713 Whether the CVS server interface is enabled for this repository.
2715 </p>
2716 </dd>
2718 gitcvs.logfile
2719 </dt>
2720 <dd>
2721 <p>
2722 Path to a log file where the CVS server interface well… logs
2724 </p>
2725 </dd>
2727 gitcvs.usecrlfattr
2728 </dt>
2729 <dd>
2730 <p>
2731 If true, the server will look up the end-of-line conversion
2733 the attributes force git to treat a file as text,
2735 treat it as text. If they suppress text conversion, the file
2737 the client might otherwise do. If the attributes do not allow
2740 </p>
2741 </dd>
2743 gitcvs.allbinary
2744 </dt>
2745 <dd>
2746 <p>
2749 unresolved files are sent to the client in
2751 as binary files, which suppresses any newline munging it
2752 otherwise might do. Alternatively, if it is set to "guess",
2753 then the contents of the file are examined to decide if
2755 </p>
2756 </dd>
2758 gitcvs.dbname
2759 </dt>
2760 <dd>
2761 <p>
2762 Database used by git-cvsserver to cache revision information
2763 derived from the git repository. The exact meaning depends on the
2764 used database driver, for SQLite (which is the default driver) this
2765 is a filename. Supports variable substitution (see
2766 <a href="git-cvsserver.html">git-cvsserver(1)</a> for details). May not contain semicolons (<tt>;</tt>).
2768 </p>
2769 </dd>
2771 gitcvs.dbdriver
2772 </dt>
2773 <dd>
2774 <p>
2775 Used Perl DBI driver. You can specify any available driver
2776 for this here, but it might not work. git-cvsserver is tested
2781 </p>
2782 </dd>
2784 gitcvs.dbuser, gitcvs.dbpass
2785 </dt>
2786 <dd>
2787 <p>
2789 since SQLite has no concept of database users and/or passwords.
2792 </p>
2793 </dd>
2795 gitcvs.dbTableNamePrefix
2796 </dt>
2797 <dd>
2798 <p>
2799 Database table name prefix. Prepended to the names of any
2800 database tables used, allowing a single database to be used
2801 for several repositories. Supports variable substitution (see
2803 characters will be replaced with underscores.
2804 </p>
2805 </dd>
2806 </dl></div>
2811 access method.</p></div>
2814 grep.lineNumber
2815 </dt>
2816 <dd>
2817 <p>
2819 </p>
2820 </dd>
2822 grep.extendedRegexp
2823 </dt>
2824 <dd>
2825 <p>
2827 </p>
2828 </dd>
2830 gui.commitmsgwidth
2831 </dt>
2832 <dd>
2833 <p>
2834 Defines how wide the commit message window is in the
2836 </p>
2837 </dd>
2839 gui.diffcontext
2840 </dt>
2841 <dd>
2842 <p>
2843 Specifies how many context lines should be used in calls to diff
2845 </p>
2846 </dd>
2848 gui.encoding
2849 </dt>
2850 <dd>
2851 <p>
2852 Specifies the default encoding to use for displaying of
2856 If this option is not set, the tools default to the
2857 locale encoding.
2858 </p>
2859 </dd>
2861 gui.matchtrackingbranch
2862 </dt>
2863 <dd>
2864 <p>
2866 default to tracking remote branches with matching names or
2867 not. Default: "false".
2868 </p>
2869 </dd>
2871 gui.newbranchtemplate
2872 </dt>
2873 <dd>
2874 <p>
2875 Is used as suggested name when creating new branches using the
2877 </p>
2878 </dd>
2880 gui.pruneduringfetch
2881 </dt>
2882 <dd>
2883 <p>
2885 performing a fetch. The default value is "false".
2886 </p>
2887 </dd>
2889 gui.trustmtime
2890 </dt>
2891 <dd>
2892 <p>
2894 timestamp or not. By default the timestamps are not trusted.
2895 </p>
2896 </dd>
2898 gui.spellingdictionary
2899 </dt>
2900 <dd>
2901 <p>
2902 Specifies the dictionary used for spell checking commit messages in
2904 off.
2905 </p>
2906 </dd>
2908 gui.fastcopyblame
2909 </dt>
2910 <dd>
2911 <p>
2913 location detection. It makes blame significantly faster on huge
2914 repositories at the expense of less thorough copy detection.
2915 </p>
2916 </dd>
2918 gui.copyblamethreshold
2919 </dt>
2920 <dd>
2921 <p>
2923 detection, measured in alphanumeric characters. See the
2925 </p>
2926 </dd>
2928 gui.blamehistoryctx
2929 </dt>
2930 <dd>
2931 <p>
2932 Specifies the radius of history context in days to show in
2935 variable is set to zero, the whole history is shown.
2936 </p>
2937 </dd>
2940 </dt>
2941 <dd>
2942 <p>
2943 Specifies the shell command line to execute when the corresponding item
2945 mandatory for every tool. The command is executed from the root of
2946 the working directory, and in the environment it receives the name of
2950 </p>
2951 </dd>
2954 </dt>
2955 <dd>
2956 <p>
2957 Run the tool only if a diff is selected in the GUI. It guarantees
2959 </p>
2960 </dd>
2963 </dt>
2964 <dd>
2965 <p>
2966 Run the command silently, without creating a window to display its
2967 output.
2968 </p>
2969 </dd>
2972 </dt>
2973 <dd>
2974 <p>
2975 Don’t rescan the working directory for changes after the tool
2976 finishes execution.
2977 </p>
2978 </dd>
2981 </dt>
2982 <dd>
2983 <p>
2984 Show a confirmation dialog before actually running the tool.
2985 </p>
2986 </dd>
2989 </dt>
2990 <dd>
2991 <p>
2992 Request a string argument from the user, and pass it to the tool
2996 the dialog uses a built-in generic prompt; otherwise the exact
2997 value of the variable is used.
2998 </p>
2999 </dd>
3002 </dt>
3003 <dd>
3004 <p>
3005 Request a single valid revision from the user, and set the
3008 </p>
3009 </dd>
3012 </dt>
3013 <dd>
3014 <p>
3016 This is useful for tools similar to merge or rebase, but not
3017 for things like checkout or reset.
3018 </p>
3019 </dd>
3022 </dt>
3023 <dd>
3024 <p>
3025 Specifies the title to use for the prompt dialog. The default
3026 is the tool name.
3027 </p>
3028 </dd>
3031 </dt>
3032 <dd>
3033 <p>
3034 Specifies the general prompt string to display at the top of
3036 The default value includes the actual command.
3037 </p>
3038 </dd>
3040 help.browser
3041 </dt>
3042 <dd>
3043 <p>
3044 Specify the browser that will be used to display help in the
3046 </p>
3047 </dd>
3049 help.format
3050 </dt>
3051 <dd>
3052 <p>
3054 Values <em>man</em>, <em>info</em>, <em>web</em> and <em>html</em> are supported. <em>man</em> is
3056 </p>
3057 </dd>
3059 help.autocorrect
3060 </dt>
3061 <dd>
3062 <p>
3063 Automatically correct and execute mistyped commands after
3064 waiting for the given number of deciseconds (0.1 sec). If more
3065 than one command can be deduced from the entered text, nothing
3066 will be executed. If the value of this option is negative,
3067 the corrected command will be executed immediately. If the
3068 value is 0 - the command will be just shown but not executed.
3069 This is the default.
3070 </p>
3071 </dd>
3073 http.proxy
3074 </dt>
3075 <dd>
3076 <p>
3080 </p>
3081 </dd>
3083 http.sslVerify
3084 </dt>
3085 <dd>
3086 <p>
3087 Whether to verify the SSL certificate when fetching or pushing
3089 variable.
3090 </p>
3091 </dd>
3093 http.sslCert
3094 </dt>
3095 <dd>
3096 <p>
3097 File containing the SSL certificate when fetching or pushing
3099 variable.
3100 </p>
3101 </dd>
3103 http.sslKey
3104 </dt>
3105 <dd>
3106 <p>
3107 File containing the SSL private key when fetching or pushing
3109 variable.
3110 </p>
3111 </dd>
3113 http.sslCertPasswordProtected
3114 </dt>
3115 <dd>
3116 <p>
3117 Enable git’s password prompt for the SSL certificate. Otherwise
3118 OpenSSL will prompt the user, possibly many times, if the
3119 certificate or private key is encrypted. Can be overridden by the
3121 </p>
3122 </dd>
3124 http.sslCAInfo
3125 </dt>
3126 <dd>
3127 <p>
3128 File containing the certificates to verify the peer with when
3129 fetching or pushing over HTTPS. Can be overridden by the
3131 </p>
3132 </dd>
3134 http.sslCAPath
3135 </dt>
3136 <dd>
3137 <p>
3138 Path containing files with the CA certificates to verify the peer
3139 with when fetching or pushing over HTTPS. Can be overridden
3141 </p>
3142 </dd>
3144 http.maxRequests
3145 </dt>
3146 <dd>
3147 <p>
3148 How many HTTP requests to launch in parallel. Can be overridden
3150 </p>
3151 </dd>
3153 http.minSessions
3154 </dt>
3155 <dd>
3156 <p>
3157 The number of curl sessions (counted across slots) to be kept across
3158 requests. They will not be ended with curl_easy_cleanup() until
3159 http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this
3161 </p>
3162 </dd>
3164 http.postBuffer
3165 </dt>
3166 <dd>
3167 <p>
3168 Maximum size in bytes of the buffer used by smart HTTP
3169 transports when POSTing data to the remote system.
3170 For requests larger than this buffer size, HTTP/1.1 and
3171 Transfer-Encoding: chunked is used to avoid creating a
3172 massive pack file locally. Default is 1 MiB, which is
3173 sufficient for most requests.
3174 </p>
3175 </dd>
3177 http.lowSpeedLimit, http.lowSpeedTime
3178 </dt>
3179 <dd>
3180 <p>
3185 </p>
3186 </dd>
3188 http.noEPSV
3189 </dt>
3190 <dd>
3191 <p>
3192 A boolean which disables using of EPSV ftp command by curl.
3195 environment variable. Default is false (curl will use EPSV).
3196 </p>
3197 </dd>
3199 http.useragent
3200 </dt>
3201 <dd>
3202 <p>
3203 The HTTP USER_AGENT string presented to an HTTP server. The default
3204 value represents the version of the client git such as git/1.7.1.
3205 This option allows you to override this value to a more common value
3206 such as Mozilla/4.0. This may be necessary, for instance, if
3207 connecting through a firewall that restricts HTTP connections to a set
3208 of common USER_AGENT strings (but not including those like git/1.7.1).
3210 </p>
3211 </dd>
3213 i18n.commitEncoding
3214 </dt>
3215 <dd>
3216 <p>
3217 Character encoding the commit messages are stored in; git itself
3218 does not care per se, but this information is necessary e.g. when
3219 importing commits from emails or in the gitk graphical history
3220 browser (and possibly at other places in the future or in other
3221 porcelains). See e.g. <a href="git-mailinfo.html">git-mailinfo(1)</a>. Defaults to <em>utf-8</em>.
3222 </p>
3223 </dd>
3225 i18n.logOutputEncoding
3226 </dt>
3227 <dd>
3228 <p>
3229 Character encoding the commit messages are converted to when
3231 </p>
3232 </dd>
3234 imap
3235 </dt>
3236 <dd>
3237 <p>
3240 </p>
3241 </dd>
3243 init.templatedir
3244 </dt>
3245 <dd>
3246 <p>
3247 Specify the directory from which templates will be copied.
3249 </p>
3250 </dd>
3252 instaweb.browser
3253 </dt>
3254 <dd>
3255 <p>
3256 Specify the program that will be used to browse your working
3258 </p>
3259 </dd>
3261 instaweb.httpd
3262 </dt>
3263 <dd>
3264 <p>
3265 The HTTP daemon command-line to start gitweb on your working
3267 </p>
3268 </dd>
3270 instaweb.local
3271 </dt>
3272 <dd>
3273 <p>
3275 be bound to the local IP (127.0.0.1).
3276 </p>
3277 </dd>
3279 instaweb.modulepath
3280 </dt>
3281 <dd>
3282 <p>
3284 instead of /usr/lib/apache2/modules. Only used if httpd
3285 is Apache.
3286 </p>
3287 </dd>
3289 instaweb.port
3290 </dt>
3291 <dd>
3292 <p>
3293 The port number to bind the gitweb httpd to. See
3295 </p>
3296 </dd>
3298 interactive.singlekey
3299 </dt>
3300 <dd>
3301 <p>
3302 In interactive commands, allow the user to provide one-letter
3303 input with a single key (i.e., without hitting enter).
3305 <a href="git-add.html">git-add(1)</a>, <a href="git-checkout.html">git-checkout(1)</a>, <a href="git-commit.html">git-commit(1)</a>,
3306 <a href="git-reset.html">git-reset(1)</a>, and <a href="git-stash.html">git-stash(1)</a>. Note that this
3307 setting is silently ignored if portable keystroke input
3308 is not available.
3309 </p>
3310 </dd>
3312 log.date
3313 </dt>
3314 <dd>
3315 <p>
3319 <tt>default</tt>, <tt>iso</tt>, <tt>rfc</tt>, and <tt>short</tt>; see <a href="git-log.html">git-log(1)</a>
3320 for details.
3321 </p>
3322 </dd>
3324 log.decorate
3325 </dt>
3326 <dd>
3327 <p>
3328 Print out the ref names of any commits that are shown by the log
3331 specified, the full ref name (including prefix) will be printed.
3333 </p>
3334 </dd>
3336 log.showroot
3337 </dt>
3338 <dd>
3339 <p>
3340 If true, the initial commit will be shown as a big creation event.
3341 This is equivalent to a diff against an empty tree.
3342 Tools like <a href="git-log.html">git-log(1)</a> or <a href="git-whatchanged.html">git-whatchanged(1)</a>, which
3343 normally hide the root commit will now show it. True by default.
3344 </p>
3345 </dd>
3347 mailmap.file
3348 </dt>
3349 <dd>
3350 <p>
3351 The location of an augmenting mailmap file. The default
3352 mailmap, located in the root of the repository, is loaded
3353 first, then the mailmap file pointed to by this variable.
3354 The location of the mailmap file may be in a repository
3355 subdirectory, or somewhere outside of the repository itself.
3356 See <a href="git-shortlog.html">git-shortlog(1)</a> and <a href="git-blame.html">git-blame(1)</a>.
3357 </p>
3358 </dd>
3360 man.viewer
3361 </dt>
3362 <dd>
3363 <p>
3364 Specify the programs that may be used to display help in the
3366 </p>
3367 </dd>
3370 </dt>
3371 <dd>
3372 <p>
3373 Specify the command to invoke the specified man viewer. The
3374 specified command is evaluated in shell with the man page
3376 </p>
3377 </dd>
3380 </dt>
3381 <dd>
3382 <p>
3383 Override the path for the given tool that may be used to
3385 </p>
3386 </dd>
3388 merge.conflictstyle
3389 </dt>
3390 <dd>
3391 <p>
3392 Specify the style in which conflicted hunks are written out to
3393 working tree files upon merge. The default is "merge", which
3396 a <tt>>>>>>>></tt> marker. An alternate style, "diff3", adds a <tt>|||||||</tt>
3398 </p>
3399 </dd>
3401 merge.defaultToUpstream
3402 </dt>
3403 <dd>
3404 <p>
3405 If merge is called without any commit argument, merge the upstream
3406 branches configured for the current branch by using their last
3407 observed values stored in their remote tracking branches.
3411 to their corresponding remote tracking branches, and the tips of
3412 these tracking branches are merged.
3413 </p>
3414 </dd>
3416 merge.ff
3417 </dt>
3418 <dd>
3419 <p>
3420 By default, git does not create an extra merge commit when merging
3421 a commit that is a descendant of the current commit. Instead, the
3423 this variable tells git to create an extra merge commit in such
3427 command line).
3428 </p>
3429 </dd>
3431 merge.log
3432 </dt>
3433 <dd>
3434 <p>
3435 In addition to branch names, populate the log message with at
3436 most the specified number of one-line descriptions from the
3437 actual commits that are being merged. Defaults to false, and
3438 true is a synonym for 20.
3439 </p>
3440 </dd>
3442 merge.renameLimit
3443 </dt>
3444 <dd>
3445 <p>
3446 The number of files to consider when performing rename detection
3447 during a merge; if not specified, defaults to the value of
3448 diff.renameLimit.
3449 </p>
3450 </dd>
3452 merge.renormalize
3453 </dt>
3454 <dd>
3455 <p>
3456 Tell git that canonical representation of files in the
3457 repository has changed over time (e.g. earlier commits record
3458 text files with CRLF line endings, but recent ones use LF line
3459 endings). In such a repository, git can convert the data
3460 recorded in commits to a canonical form before performing a
3461 merge to reduce unnecessary conflicts. For more information,
3462 see section "Merging branches with differing checkin/checkout
3464 </p>
3465 </dd>
3467 merge.stat
3468 </dt>
3469 <dd>
3470 <p>
3471 Whether to print the diffstat between ORIG_HEAD and the merge result
3472 at the end of the merge. True by default.
3473 </p>
3474 </dd>
3476 merge.tool
3477 </dt>
3478 <dd>
3479 <p>
3480 Controls which merge resolution program is used by
3484 and "xxdiff". Any other value is treated is custom merge tool
3486 </p>
3487 </dd>
3489 merge.verbosity
3490 </dt>
3491 <dd>
3492 <p>
3493 Controls the amount of output shown by the recursive merge
3494 strategy. Level 0 outputs nothing except a final error
3495 message if conflicts were detected. Level 1 outputs only
3497 above outputs debugging information. The default is level 2.
3499 </p>
3500 </dd>
3503 </dt>
3504 <dd>
3505 <p>
3506 Defines a human-readable name for a custom low-level
3508 </p>
3509 </dd>
3512 </dt>
3513 <dd>
3514 <p>
3515 Defines the command that implements a custom low-level
3517 </p>
3518 </dd>
3521 </dt>
3522 <dd>
3523 <p>
3524 Names a low-level merge driver to be used when
3525 performing an internal merge between common ancestors.
3527 </p>
3528 </dd>
3531 </dt>
3532 <dd>
3533 <p>
3534 Override the path for the given tool. This is useful in case
3535 your tool is not in the PATH.
3536 </p>
3537 </dd>
3540 </dt>
3541 <dd>
3542 <p>
3543 Specify the command to invoke the specified merge tool. The
3544 specified command is evaluated in shell with the following
3546 containing the common base of the files to be merged, if available;
3549 file containing the contents of the file from the branch being
3551 tool should write the results of a successful merge.
3552 </p>
3553 </dd>
3556 </dt>
3557 <dd>
3558 <p>
3559 For a custom merge command, specify whether the exit code of
3560 the merge command can be used to determine whether the merge was
3561 successful. If this is not set to true then the merge target file
3562 timestamp is checked and the merge assumed to have been successful
3563 if the file has been updated, otherwise the user is prompted to
3564 indicate the success of the merge.
3565 </p>
3566 </dd>
3568 mergetool.keepBackup
3569 </dt>
3570 <dd>
3571 <p>
3572 After performing a merge, the original file with conflict markers
3576 </p>
3577 </dd>
3579 mergetool.keepTemporaries
3580 </dt>
3581 <dd>
3582 <p>
3583 When invoking a custom merge tool, git uses a set of temporary
3584 files to pass to the tool. If the tool returns an error and this
3586 preserved, otherwise they will be removed after the tool has
3588 </p>
3589 </dd>
3591 mergetool.prompt
3592 </dt>
3593 <dd>
3594 <p>
3595 Prompt before each invocation of the merge resolution program.
3596 </p>
3597 </dd>
3599 notes.displayRef
3600 </dt>
3601 <dd>
3602 <p>
3603 The (fully qualified) refname from which to show notes when
3604 showing commit messages. The value of this variable can be set
3605 to a glob, in which case notes from all matching refs will be
3606 shown. You may also specify this configuration variable
3607 several times. A warning will be issued for refs that do not
3608 exist, but a glob that does not match any refs is silently
3609 ignored.
3610 </p>
3611 <div class="paragraph"><p>This setting can be overridden with the <tt>GIT_NOTES_DISPLAY_REF</tt>
3612 environment variable, which must be a colon separated list of refs or
3613 globs.</p></div>
3615 GIT_NOTES_REF) is also implicitly added to the list of refs to be
3616 displayed.</p></div>
3617 </dd>
3620 </dt>
3621 <dd>
3622 <p>
3625 automatically copies your notes from the original to the
3627 "notes.rewriteRef" below.
3628 </p>
3629 </dd>
3631 notes.rewriteMode
3632 </dt>
3633 <dd>
3634 <p>
3635 When copying notes during a rewrite (see the
3636 "notes.rewrite.<command>" option), determines what to do if
3637 the target commit already has a note. Must be one of
3640 </p>
3641 <div class="paragraph"><p>This setting can be overridden with the <tt>GIT_NOTES_REWRITE_MODE</tt>
3642 environment variable.</p></div>
3643 </dd>
3645 notes.rewriteRef
3646 </dt>
3647 <dd>
3648 <p>
3649 When copying notes during a rewrite, specifies the (fully
3650 qualified) ref whose notes should be copied. The ref may be a
3651 glob, in which case notes in all matching refs will be copied.
3652 You may also specify this configuration several times.
3653 </p>
3655 enable note rewriting.</p></div>
3656 <div class="paragraph"><p>This setting can be overridden with the <tt>GIT_NOTES_REWRITE_REF</tt>
3657 environment variable, which must be a colon separated list of refs or
3658 globs.</p></div>
3659 </dd>
3661 pack.window
3662 </dt>
3663 <dd>
3664 <p>
3666 window size is given on the command line. Defaults to 10.
3667 </p>
3668 </dd>
3670 pack.depth
3671 </dt>
3672 <dd>
3673 <p>
3674 The maximum delta depth used by <a href="git-pack-objects.html">git-pack-objects(1)</a> when no
3675 maximum depth is given on the command line. Defaults to 50.
3676 </p>
3677 </dd>
3679 pack.windowMemory
3680 </dt>
3681 <dd>
3682 <p>
3684 when no limit is given on the command line. The value can be
3686 limit.
3687 </p>
3688 </dd>
3690 pack.compression
3691 </dt>
3692 <dd>
3693 <p>
3697 slowest. If not set, defaults to core.compression. If that is
3699 compromise between speed and compression (currently equivalent
3700 to level 6)."
3701 </p>
3702 <div class="paragraph"><p>Note that changing the compression level will not automatically recompress
3703 all existing objects. You can force recompression by passing the -F option
3705 </dd>
3707 pack.deltaCacheSize
3708 </dt>
3709 <dd>
3710 <p>
3711 The maximum memory in bytes used for caching deltas in
3713 This cache is used to speed up the writing object phase by not
3714 having to recompute the final delta result once the best match
3715 for all objects is found. Repacking large repositories on machines
3716 which are tight with memory might be badly impacted by this though,
3717 especially if this cache pushes the system into swapping.
3719 used to virtually disable this cache. Defaults to 256 MiB.
3720 </p>
3721 </dd>
3723 pack.deltaCacheLimit
3724 </dt>
3725 <dd>
3726 <p>
3727 The maximum size of a delta, that is cached in
3729 writing object phase by not having to recompute the final delta
3730 result once the best match for all objects is found. Defaults to 1000.
3731 </p>
3732 </dd>
3734 pack.threads
3735 </dt>
3736 <dd>
3737 <p>
3738 Specifies the number of threads to spawn when searching for best
3740 be compiled with pthreads otherwise this option is ignored with a
3741 warning. This is meant to reduce packing time on multiprocessor
3742 machines. The required amount of memory for the delta search window
3743 is however multiplied by the number of threads.
3745 and set the number of threads accordingly.
3746 </p>
3747 </dd>
3749 pack.indexVersion
3750 </dt>
3751 <dd>
3752 <p>
3753 Specify the default pack index version. Valid values are 1 for
3755 the new pack index with capabilities for packs larger than 4 GB
3756 as well as proper protection against the repacking of corrupted
3758 and this config option ignored whenever the corresponding pack is
3759 larger than 2 GB.
3760 </p>
3761 <div class="paragraph"><p>If you have an old git that does not understand the version 2 <tt>*.idx</tt> file,
3763 that will copy both <tt>*.pack</tt> file and corresponding <tt>*.idx</tt> file from the
3764 other side may give you a repository that cannot be accessed with your
3766 you can use <a href="git-index-pack.html">git-index-pack(1)</a> on the *.pack file to regenerate
3768 </dd>
3770 pack.packSizeLimit
3771 </dt>
3772 <dd>
3773 <p>
3774 The maximum size of a pack. This setting only affects
3775 packing to a file when repacking, i.e. the git:// protocol
3778 limited to 1 MiB. The default is unlimited.
3780 supported.
3781 </p>
3782 </dd>
3785 </dt>
3786 <dd>
3787 <p>
3788 If the value is boolean, turns on or off pagination of the
3789 output of a particular git subcommand when writing to a tty.
3790 Otherwise, turns on pagination for the subcommand using the
3793 precedence over this option. To disable pagination for all
3795 </p>
3796 </dd>
3799 </dt>
3800 <dd>
3801 <p>
3802 Alias for a --pretty= format string, as specified in
3804 as the built-in pretty formats could. For example,
3808 Note that an alias with the same name as a built-in format
3809 will be silently ignored.
3810 </p>
3811 </dd>
3813 pull.octopus
3814 </dt>
3815 <dd>
3816 <p>
3817 The default merge strategy to use when pulling multiple branches
3818 at once.
3819 </p>
3820 </dd>
3822 pull.twohead
3823 </dt>
3824 <dd>
3825 <p>
3826 The default merge strategy to use when pulling a single branch.
3827 </p>
3828 </dd>
3830 push.default
3831 </dt>
3832 <dd>
3833 <p>
3834 Defines the action git push should take if no refspec is given
3835 on the command line, no refspec is configured in the remote, and
3836 no refspec is implied by any of the options given on the command
3837 line. Possible values are:
3838 </p>
3840 <li>
3841 <p>
3843 </p>
3844 </li>
3845 <li>
3846 <p>
3848 All branches having the same name in both ends are considered to be
3849 matching. This is the default.
3850 </p>
3851 </li>
3852 <li>
3853 <p>
3855 </p>
3856 </li>
3857 <li>
3858 <p>
3860 </p>
3861 </li>
3862 <li>
3863 <p>
3865 </p>
3866 </li>
3867 </ul></div>
3868 </dd>
3870 rebase.stat
3871 </dt>
3872 <dd>
3873 <p>
3874 Whether to show a diffstat of what changed upstream since the last
3875 rebase. False by default.
3876 </p>
3877 </dd>
3879 rebase.autosquash
3880 </dt>
3881 <dd>
3882 <p>
3884 </p>
3885 </dd>
3887 receive.autogc
3888 </dt>
3889 <dd>
3890 <p>
3891 By default, git-receive-pack will run "git-gc --auto" after
3892 receiving data from git-push and updating refs. You can stop
3893 it by setting this variable to false.
3894 </p>
3895 </dd>
3897 receive.fsckObjects
3898 </dt>
3899 <dd>
3900 <p>
3901 If it is set to true, git-receive-pack will check all received
3902 objects. It will abort in the case of a malformed object or a
3903 broken link. The result of an abort are only dangling objects.
3904 Defaults to false.
3905 </p>
3906 </dd>
3908 receive.unpackLimit
3909 </dt>
3910 <dd>
3911 <p>
3912 If the number of objects received in a push is below this
3913 limit then the objects will be unpacked into loose object
3914 files. However if the number of received objects equals or
3915 exceeds this limit then the received pack will be stored as
3916 a pack, after adding any missing delta bases. Storing the
3917 pack from a push can make the push operation complete faster,
3918 especially on slow filesystems. If not set, the value of
3920 </p>
3921 </dd>
3923 receive.denyDeletes
3924 </dt>
3925 <dd>
3926 <p>
3927 If set to true, git-receive-pack will deny a ref update that deletes
3928 the ref. Use this to prevent such a ref deletion via a push.
3929 </p>
3930 </dd>
3932 receive.denyDeleteCurrent
3933 </dt>
3934 <dd>
3935 <p>
3936 If set to true, git-receive-pack will deny a ref update that
3937 deletes the currently checked out branch of a non-bare repository.
3938 </p>
3939 </dd>
3941 receive.denyCurrentBranch
3942 </dt>
3943 <dd>
3944 <p>
3945 If set to true or "refuse", git-receive-pack will deny a ref update
3946 to the currently checked out branch of a non-bare repository.
3947 Such a push is potentially dangerous because it brings the HEAD
3948 out of sync with the index and working tree. If set to "warn",
3949 print a warning of such a push to stderr, but allow the push to
3950 proceed. If set to false or "ignore", allow such pushes with no
3951 message. Defaults to "refuse".
3952 </p>
3953 </dd>
3955 receive.denyNonFastForwards
3956 </dt>
3957 <dd>
3958 <p>
3959 If set to true, git-receive-pack will deny a ref update which is
3960 not a fast-forward. Use this to prevent such an update via a push,
3961 even if that push is forced. This configuration variable is
3962 set when initializing a shared repository.
3963 </p>
3964 </dd>
3966 receive.updateserverinfo
3967 </dt>
3968 <dd>
3969 <p>
3970 If set to true, git-receive-pack will run git-update-server-info
3971 after receiving data from git-push and updating refs.
3972 </p>
3973 </dd>
3976 </dt>
3977 <dd>
3978 <p>
3981 </p>
3982 </dd>
3985 </dt>
3986 <dd>
3987 <p>
3989 </p>
3990 </dd>
3993 </dt>
3994 <dd>
3995 <p>
3996 For remotes that require curl (http, https and ftp), the URL to
3997 the proxy to use for that remote. Set to the empty string to
3998 disable proxying for that remote.
3999 </p>
4000 </dd>
4003 </dt>
4004 <dd>
4005 <p>
4008 </p>
4009 </dd>
4012 </dt>
4013 <dd>
4014 <p>
4017 </p>
4018 </dd>
4021 </dt>
4022 <dd>
4023 <p>
4024 If true, pushing to this remote will automatically behave
4026 </p>
4027 </dd>
4030 </dt>
4031 <dd>
4032 <p>
4033 If true, this remote will be skipped by default when updating
4036 </p>
4037 </dd>
4040 </dt>
4041 <dd>
4042 <p>
4043 If true, this remote will be skipped by default when updating
4046 </p>
4047 </dd>
4050 </dt>
4051 <dd>
4052 <p>
4053 The default program to execute on the remote side when pushing. See
4055 </p>
4056 </dd>
4059 </dt>
4060 <dd>
4061 <p>
4062 The default program to execute on the remote side when fetching. See
4064 </p>
4065 </dd>
4068 </dt>
4069 <dd>
4070 <p>
4071 Setting this value to --no-tags disables automatic tag following when
4075 override this setting. See options --tags and --no-tags of
4077 </p>
4078 </dd>
4081 </dt>
4082 <dd>
4083 <p>
4086 </p>
4087 </dd>
4090 </dt>
4091 <dd>
4092 <p>
4093 The list of remotes which are fetched by "git remote update
4095 </p>
4096 </dd>
4098 repack.usedeltabaseoffset
4099 </dt>
4100 <dd>
4101 <p>
4103 delta-base offset. If you need to share your repository with
4104 git older than version 1.4.4, either directly or via a dumb
4105 protocol such as http, then you need to set this option to
4106 "false" and repack. Access from old git versions over the
4107 native protocol are unaffected by this option.
4108 </p>
4109 </dd>
4111 rerere.autoupdate
4112 </dt>
4113 <dd>
4114 <p>
4116 resulting contents after it cleanly resolves conflicts using
4117 previously recorded resolution. Defaults to false.
4118 </p>
4119 </dd>
4121 rerere.enabled
4122 </dt>
4123 <dd>
4124 <p>
4125 Activate recording of resolved conflicts, so that identical
4126 conflict hunks can be resolved automatically, should they
4130 </p>
4131 </dd>
4133 sendemail.identity
4134 </dt>
4135 <dd>
4136 <p>
4137 A configuration identity. When given, causes values in the
4141 </p>
4142 </dd>
4144 sendemail.smtpencryption
4145 </dt>
4146 <dd>
4147 <p>
4150 </p>
4151 </dd>
4153 sendemail.smtpssl
4154 </dt>
4155 <dd>
4156 <p>
4158 </p>
4159 </dd>
4162 </dt>
4163 <dd>
4164 <p>
4166 found below, taking precedence over those when the this
4167 identity is selected, through command-line or
4169 </p>
4170 </dd>
4172 sendemail.aliasesfile
4173 </dt>
4175 sendemail.aliasfiletype
4176 </dt>
4178 sendemail.bcc
4179 </dt>
4181 sendemail.cc
4182 </dt>
4184 sendemail.cccmd
4185 </dt>
4187 sendemail.chainreplyto
4188 </dt>
4190 sendemail.confirm
4191 </dt>
4193 sendemail.envelopesender
4194 </dt>
4196 sendemail.from
4197 </dt>
4199 sendemail.multiedit
4200 </dt>
4202 sendemail.signedoffbycc
4203 </dt>
4205 sendemail.smtppass
4206 </dt>
4208 sendemail.suppresscc
4209 </dt>
4211 sendemail.suppressfrom
4212 </dt>
4214 sendemail.to
4215 </dt>
4217 sendemail.smtpdomain
4218 </dt>
4220 sendemail.smtpserver
4221 </dt>
4223 sendemail.smtpserverport
4224 </dt>
4226 sendemail.smtpserveroption
4227 </dt>
4229 sendemail.smtpuser
4230 </dt>
4232 sendemail.thread
4233 </dt>
4235 sendemail.validate
4236 </dt>
4237 <dd>
4238 <p>
4240 </p>
4241 </dd>
4243 sendemail.signedoffcc
4244 </dt>
4245 <dd>
4246 <p>
4248 </p>
4249 </dd>
4251 showbranch.default
4252 </dt>
4253 <dd>
4254 <p>
4257 </p>
4258 </dd>
4260 status.relativePaths
4261 </dt>
4262 <dd>
4263 <p>
4266 relative to the repository root (this was the default for git
4267 prior to v1.5.4).
4268 </p>
4269 </dd>
4271 status.showUntrackedFiles
4272 </dt>
4273 <dd>
4274 <p>
4275 By default, <a href="git-status.html">git-status(1)</a> and <a href="git-commit.html">git-commit(1)</a> show
4276 files which are not currently tracked by Git. Directories which
4277 contain only untracked files, are shown with the directory name
4278 only. Showing untracked files means that Git needs to lstat() all
4279 all the files in the whole repository, which might be slow on some
4280 systems. So, this variable controls how the commands displays
4281 the untracked files. Possible values are:
4282 </p>
4284 <li>
4285 <p>
4287 </p>
4288 </li>
4289 <li>
4290 <p>
4292 </p>
4293 </li>
4294 <li>
4295 <p>
4297 </p>
4298 </li>
4299 </ul></div>
4301 This variable can be overridden with the -u|--untracked-files option
4302 of <a href="git-status.html">git-status(1)</a> and <a href="git-commit.html">git-commit(1)</a>.</p></div>
4303 </dd>
4305 status.submodulesummary
4306 </dt>
4307 <dd>
4308 <p>
4309 Defaults to false.
4310 If this is set to a non zero number or true (identical to -1 or an
4311 unlimited number), the submodule summary will be enabled and a
4312 summary of commits for modified submodules will be shown (see
4314 </p>
4315 </dd>
4318 </dt>
4321 </dt>
4324 </dt>
4325 <dd>
4326 <p>
4327 The path within this project, URL, and the updating strategy
4328 for a submodule. These variables are initially populated
4331 <a href="git-submodule.html">git-submodule(1)</a> and <a href="gitmodules.html">gitmodules(5)</a> for details.
4332 </p>
4333 </dd>
4336 </dt>
4337 <dd>
4338 <p>
4339 This option can be used to control recursive fetching of this
4340 submodule. It can be overridden by using the --[no-]recurse-submodules
4343 file.
4344 </p>
4345 </dd>
4348 </dt>
4349 <dd>
4350 <p>
4351 Defines under what circumstances "git status" and the diff family show
4352 a submodule as modified. When set to "all", it will never be considered
4353 modified, "dirty" will ignore all changes to the submodules work tree and
4354 takes only differences between the HEAD of the submodule and the commit
4355 recorded in the superproject into account. "untracked" will additionally
4356 let submodules with modified tracked files in their work tree show up.
4357 Using "none" (the default when this option is not set) also shows
4358 submodules that have untracked files in their work tree as changed.
4359 This setting overrides any setting made in .gitmodules for this submodule,
4360 both settings can be overridden on the command line by using the
4361 "--ignore-submodules" option.
4362 </p>
4363 </dd>
4365 tar.umask
4366 </dt>
4367 <dd>
4368 <p>
4369 This variable can be used to restrict the permission bits of
4370 tar archive entries. The default is 0002, which turns off the
4371 world write bit. The special value "user" indicates that the
4374 </p>
4375 </dd>
4377 transfer.unpackLimit
4378 </dt>
4379 <dd>
4380 <p>
4382 not set, the value of this variable is used instead.
4383 The default value is 100.
4384 </p>
4385 </dd>
4388 </dt>
4389 <dd>
4390 <p>
4391 Any URL that starts with this value will be rewritten to
4393 large number of repositories, and serves them with multiple
4394 access methods, and some users need to use different access
4395 methods, this feature allows people to specify any of the
4396 equivalent URLs and have git automatically rewrite the URL to
4397 the best alternative for the particular user, even for a
4398 never-before-seen repository on the site. When more than one
4399 insteadOf strings match a given URL, the longest match is used.
4400 </p>
4401 </dd>
4404 </dt>
4405 <dd>
4406 <p>
4407 Any URL that starts with this value will not be pushed to;
4409 resulting URL will be pushed to. In cases where some site serves
4410 a large number of repositories, and serves them with multiple
4411 access methods, some of which do not allow push, this feature
4412 allows people to specify a pull-only URL and have git
4413 automatically use an appropriate URL to push, even for a
4414 never-before-seen repository on the site. When more than one
4415 pushInsteadOf strings match a given URL, the longest match is
4416 used. If a remote has an explicit pushurl, git will ignore this
4417 setting for that remote.
4418 </p>
4419 </dd>
4421 user.email
4422 </dt>
4423 <dd>
4424 <p>
4425 Your email address to be recorded in any newly created commits.
4427 <em>EMAIL</em> environment variables. See <a href="git-commit-tree.html">git-commit-tree(1)</a>.
4428 </p>
4429 </dd>
4431 user.name
4432 </dt>
4433 <dd>
4434 <p>
4435 Your full name to be recorded in any newly created commits.
4438 </p>
4439 </dd>
4441 user.signingkey
4442 </dt>
4443 <dd>
4444 <p>
4446 automatically when creating a signed tag, you can override the
4447 default selection with this variable. This option is passed
4448 unchanged to gpg’s --local-user parameter, so you may specify a key
4449 using any method that gpg supports.
4450 </p>
4451 </dd>
4453 web.browser
4454 </dt>
4455 <dd>
4456 <p>
4457 Specify a web browser that may be used by some commands.
4458 Currently only <a href="git-instaweb.html">git-instaweb(1)</a> and <a href="git-help.html">git-help(1)</a>
4459 may use it.
4460 </p>
4461 </dd>
4462 </dl></div>
4463 </div>
4467 </div>
4471 </div>
4472 </div>
4473 </body>
4474 </html>