| blob | 432c6af7681e97f672c5ff96a0544a2774eaa1d6 |
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 working tree. The value will not be
1290 used in combination with repositories found automatically in
1291 a .git directory (i.e. $GIT_DIR is not set).
1292 This can be overridden by the GIT_WORK_TREE environment
1294 an absolute path or relative path to the directory specified by
1295 --git-dir or GIT_DIR.
1296 Note: If --git-dir or GIT_DIR are specified but none of
1297 --work-tree, GIT_WORK_TREE and core.worktree is specified,
1298 the current working directory is regarded as the top directory
1299 of your working tree.
1300 </p>
1301 </dd>
1303 core.logAllRefUpdates
1304 </dt>
1305 <dd>
1306 <p>
1308 "$GIT_DIR/logs/<ref>", by appending the new and old
1309 SHA1, the date/time and the reason of the update, but
1310 only when the file exists. If this configuration
1311 variable is set to true, missing "$GIT_DIR/logs/<ref>"
1312 file is automatically created for branch heads.
1313 </p>
1317 a working directory associated with it, and false by
1318 default in a bare repository.</p></div>
1319 </dd>
1321 core.repositoryFormatVersion
1322 </dt>
1323 <dd>
1324 <p>
1325 Internal variable identifying the repository format and layout
1326 version.
1327 </p>
1328 </dd>
1330 core.sharedRepository
1331 </dt>
1332 <dd>
1333 <p>
1335 several users in a group (making sure all the files and objects are
1337 repository will be readable by all users, additionally to being
1341 user’s umask value (whereas the other options will only override
1343 the repo read/write-able for the owner and group, but inaccessible to
1345 repository that is group-readable but not group-writable.
1347 </p>
1348 </dd>
1350 core.warnAmbiguousRefs
1351 </dt>
1352 <dd>
1353 <p>
1354 If true, git will warn you if the ref name you passed it is ambiguous
1355 and might match multiple refs in the .git/refs/ tree. True by default.
1356 </p>
1357 </dd>
1359 core.abbrevguard
1360 </dt>
1361 <dd>
1362 <p>
1363 Even though git makes sure that it uses enough hexdigits to show
1364 an abbreviated object name unambiguously, as more objects are
1365 added to the repository over time, a short name that used to be
1366 unique will stop being unique. Git uses this many extra hexdigits
1367 that are more than necessary to make the object name currently
1368 unique, in the hope that its output will stay unique a bit longer.
1369 Defaults to 0.
1370 </p>
1371 </dd>
1373 core.compression
1374 </dt>
1375 <dd>
1376 <p>
1380 If set, this provides a default to other compression variables,
1382 </p>
1383 </dd>
1385 core.loosecompression
1386 </dt>
1387 <dd>
1388 <p>
1392 slowest. If not set, defaults to core.compression. If that is
1393 not set, defaults to 1 (best speed).
1394 </p>
1395 </dd>
1397 core.packedGitWindowSize
1398 </dt>
1399 <dd>
1400 <p>
1401 Number of bytes of a pack file to map into memory in a
1402 single mapping operation. Larger window sizes may allow
1403 your system to process a smaller number of large pack files
1404 more quickly. Smaller window sizes will negatively affect
1405 performance due to increased calls to the operating system’s
1406 memory manager, but may improve performance when accessing
1407 a large number of large pack files.
1408 </p>
1411 be reasonable for all users/operating systems. You probably do
1412 not need to adjust this value.</p></div>
1413 <div class="paragraph"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1414 </dd>
1416 core.packedGitLimit
1417 </dt>
1418 <dd>
1419 <p>
1420 Maximum number of bytes to map simultaneously into memory
1421 from pack files. If Git needs to access more than this many
1422 bytes at once to complete an operation it will unmap existing
1423 regions to reclaim virtual address space within the process.
1424 </p>
1425 <div class="paragraph"><p>Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms.
1426 This should be reasonable for all users/operating systems, except on
1427 the largest projects. You probably do not need to adjust this value.</p></div>
1428 <div class="paragraph"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1429 </dd>
1431 core.deltaBaseCacheLimit
1432 </dt>
1433 <dd>
1434 <p>
1435 Maximum number of bytes to reserve for caching base objects
1436 that may be referenced by multiple deltified objects. By storing the
1437 entire decompressed base objects in a cache Git is able
1438 to avoid unpacking and decompressing frequently used base
1439 objects multiple times.
1440 </p>
1442 for all users/operating systems, except on the largest projects.
1443 You probably do not need to adjust this value.</p></div>
1444 <div class="paragraph"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1445 </dd>
1447 core.bigFileThreshold
1448 </dt>
1449 <dd>
1450 <p>
1451 Files larger than this size are stored deflated, without
1452 attempting delta compression. Storing large files without
1453 delta compression avoids excessive memory usage, at the
1454 slight expense of increased disk usage.
1455 </p>
1457 for most projects as source code and other text files can still
1459 <div class="paragraph"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1460 <div class="paragraph"><p>Currently only <a href="git-fast-import.html">git-fast-import(1)</a> honors this setting.</p></div>
1461 </dd>
1463 core.excludesfile
1464 </dt>
1465 <dd>
1466 <p>
1469 of files which are not meant to be tracked. "~/" is expanded
1472 </p>
1473 </dd>
1475 core.askpass
1476 </dt>
1477 <dd>
1478 <p>
1479 Some commands (e.g. svn and http interfaces) that interactively
1480 ask for a password can be told to use an external program given
1482 environment variable. If not set, fall back to the value of the
1484 prompt. The external program shall be given a suitable prompt as
1485 command line argument and write the password on its STDOUT.
1486 </p>
1487 </dd>
1489 core.attributesfile
1490 </dt>
1491 <dd>
1492 <p>
1497 </p>
1498 </dd>
1500 core.editor
1501 </dt>
1502 <dd>
1503 <p>
1505 messages by launching an editor uses the value of this
1506 variable when it is set, and the environment variable
1508 </p>
1509 </dd>
1511 core.pager
1512 </dt>
1513 <dd>
1514 <p>
1515 The command that git will use to paginate output. Can
1519 pager. One can change these settings by setting the
1521 these settings can be overridden on a project or
1524 environment variable behaviour above, so if you want
1525 to override git’s default settings this way, you need
1526 to be explicit. For example, to disable the S option
1529 shell by git, which will translate the final command to
1531 </p>
1532 </dd>
1534 core.whitespace
1535 </dt>
1536 <dd>
1537 <p>
1538 A comma separated list of common whitespace problems to
1543 </p>
1545 <li>
1546 <p>
1548 as an error (enabled by default).
1549 </p>
1550 </li>
1551 <li>
1552 <p>
1554 before a tab character in the initial indent part of the line as an
1555 error (enabled by default).
1556 </p>
1557 </li>
1558 <li>
1559 <p>
1561 space characters as an error (not enabled by default).
1562 </p>
1563 </li>
1564 <li>
1565 <p>
1567 the line as an error (not enabled by default).
1568 </p>
1569 </li>
1570 <li>
1571 <p>
1573 (enabled by default).
1574 </p>
1575 </li>
1576 <li>
1577 <p>
1580 </p>
1581 </li>
1582 <li>
1583 <p>
1586 does not trigger if the character before such a carriage-return
1587 is not a whitespace (not enabled by default).
1588 </p>
1589 </li>
1590 <li>
1591 <p>
1595 </p>
1596 </li>
1597 </ul></div>
1598 </dd>
1600 core.fsyncobjectfiles
1601 </dt>
1602 <dd>
1603 <p>
1605 </p>
1607 data writes properly, but can be useful for filesystems that do not use
1608 journalling (traditional UNIX filesystems) or that only journal metadata
1610 </dd>
1612 core.preloadindex
1613 </dt>
1614 <dd>
1615 <p>
1617 </p>
1618 <div class="paragraph"><p>This can speed up operations like <em>git diff</em> and <em>git status</em> especially
1619 on filesystems like NFS that have weak caching semantics and thus
1621 index comparison to the filesystem data in parallel, allowing
1623 </dd>
1625 core.createObject
1626 </dt>
1627 <dd>
1628 <p>
1630 a delete of the source are used to make sure that object creation
1631 will not overwrite existing objects.
1632 </p>
1633 <div class="paragraph"><p>On some file system/operating system combinations, this is unreliable.
1635 check that makes sure that existing object files will not get overwritten.</p></div>
1636 </dd>
1638 core.notesRef
1639 </dt>
1640 <dd>
1641 <p>
1642 When showing commit messages, also show notes which are stored in
1643 the given ref. The ref must be fully qualified. If the given
1644 ref does not exist, it is not an error but means that no
1645 notes should be printed.
1646 </p>
1647 <div class="paragraph"><p>This setting defaults to "refs/notes/commits", and it can be overridden by
1648 the <em>GIT_NOTES_REF</em> environment variable. See <a href="git-notes.html">git-notes(1)</a>.</p></div>
1649 </dd>
1651 core.sparseCheckout
1652 </dt>
1653 <dd>
1654 <p>
1657 </p>
1658 </dd>
1660 add.ignore-errors
1661 </dt>
1663 add.ignoreErrors
1664 </dt>
1665 <dd>
1666 <p>
1671 convention for configuration variables. Newer versions of git
1673 </p>
1674 </dd>
1676 alias.*
1677 </dt>
1678 <dd>
1679 <p>
1681 after defining "alias.last = cat-file commit HEAD", the invocation
1683 confusion and troubles with script usage, aliases that
1684 hide existing git commands are ignored. Arguments are split by
1685 spaces, the usual shell quoting and escaping is supported.
1686 quote pair and a backslash can be used to quote them.
1687 </p>
1689 it will be treated as a shell command. For example, defining
1690 "alias.new = !gitk --all --not ORIG_HEAD", the invocation
1691 "git new" is equivalent to running the shell command
1692 "gitk --all --not ORIG_HEAD". Note that shell commands will be
1693 executed from the top-level directory of a repository, which may
1694 not necessarily be the current directory.</p></div>
1695 </dd>
1697 am.keepcr
1698 </dt>
1699 <dd>
1700 <p>
1701 If true, git-am will call git-mailsplit for patches in mbox format
1706 </p>
1707 </dd>
1709 apply.ignorewhitespace
1710 </dt>
1711 <dd>
1712 <p>
1715 option.
1717 respect all whitespace differences.
1719 </p>
1720 </dd>
1722 apply.whitespace
1723 </dt>
1724 <dd>
1725 <p>
1728 </p>
1729 </dd>
1731 branch.autosetupmerge
1732 </dt>
1733 <dd>
1734 <p>
1737 starting point branch. Note that even if this option is not set,
1741 starting point is a remote-tracking branch; <tt>always</tt> —  automatic setup is done when the starting point is either a
1742 local branch or remote-tracking
1743 branch. This option defaults to true.
1744 </p>
1745 </dd>
1747 branch.autosetuprebase
1748 </dt>
1749 <dd>
1750 <p>
1752 that tracks another branch, this variable tells git to set
1753 up pull to rebase instead of merge (see "branch.<name>.rebase").
1756 other local branches.
1758 remote-tracking branches.
1760 branches.
1761 See "branch.autosetupmerge" for details on how to set up a
1762 branch to track another branch.
1763 This option defaults to never.
1764 </p>
1765 </dd>
1768 </dt>
1769 <dd>
1770 <p>
1774 </p>
1775 </dd>
1778 </dt>
1779 <dd>
1780 <p>
1785 refspec to be marked for merging in FETCH_HEAD. The value is
1786 handled like the remote part of a refspec, and must match a
1787 ref which is fetched from the remote given by
1788 "branch.<name>.remote".
1792 Specify multiple values to get an octopus merge.
1794 another branch in the local repository, you can point
1797 </p>
1798 </dd>
1801 </dt>
1802 <dd>
1803 <p>
1806 option values containing whitespace characters are currently not
1807 supported.
1808 </p>
1809 </dd>
1812 </dt>
1813 <dd>
1814 <p>
1816 instead of merging the default branch from the default remote when
1817 "git pull" is run.
1820 for details).
1821 </p>
1822 </dd>
1825 </dt>
1826 <dd>
1827 <p>
1828 Specify the command to invoke the specified browser. The
1829 specified command is evaluated in shell with the URLs passed
1831 </p>
1832 </dd>
1835 </dt>
1836 <dd>
1837 <p>
1838 Override the path for the given tool that may be used to
1841 </p>
1842 </dd>
1844 clean.requireForce
1845 </dt>
1846 <dd>
1847 <p>
1848 A boolean to make git-clean do nothing unless given -f
1849 or -n. Defaults to true.
1850 </p>
1851 </dd>
1853 color.branch
1854 </dt>
1855 <dd>
1856 <p>
1857 A boolean to enable/disable color in the output of
1859 <tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt> (or <tt>true</tt>), in which case colors are used
1860 only when the output is to a terminal. Defaults to false.
1861 </p>
1862 </dd>
1865 </dt>
1866 <dd>
1867 <p>
1871 refs).
1872 </p>
1873 <div class="paragraph"><p>The value for these configuration variables is a list of colors (at most
1874 two) and attributes (at most one), separated by spaces. The colors
1875 accepted are <tt>normal</tt>, <tt>black</tt>, <tt>red</tt>, <tt>green</tt>, <tt>yellow</tt>, <tt>blue</tt>,
1876 <tt>magenta</tt>, <tt>cyan</tt> and <tt>white</tt>; the attributes are <tt>bold</tt>, <tt>dim</tt>, <tt>ul</tt>,
1878 second is the background. The position of the attribute, if any,
1880 </dd>
1882 color.diff
1883 </dt>
1884 <dd>
1885 <p>
1888 colors only when the output is to the terminal. Defaults to false.
1889 </p>
1890 </dd>
1893 </dt>
1894 <dd>
1895 <p>
1897 which part of the patch to use the specified color, and is one
1901 (highlighting whitespace errors). The values of these variables may be
1903 </p>
1904 </dd>
1907 </dt>
1908 <dd>
1909 <p>
1911 of <tt>branch</tt>, <tt>remoteBranch</tt>, <tt>tag</tt>, <tt>stash</tt> or <tt>HEAD</tt> for local
1912 branches, remote-tracking branches, tags, stash and HEAD, respectively.
1913 </p>
1914 </dd>
1916 color.grep
1917 </dt>
1918 <dd>
1919 <p>
1923 </p>
1924 </dd>
1927 </dt>
1928 <dd>
1929 <p>
1931 part of the line to use the specified color, and is one of
1932 </p>
1936 </dt>
1937 <dd>
1938 <p>
1940 </p>
1941 </dd>
1944 </dt>
1945 <dd>
1946 <p>
1948 </p>
1949 </dd>
1952 </dt>
1953 <dd>
1954 <p>
1956 </p>
1957 </dd>
1960 </dt>
1961 <dd>
1962 <p>
1964 </p>
1965 </dd>
1968 </dt>
1969 <dd>
1970 <p>
1971 matching text
1972 </p>
1973 </dd>
1976 </dt>
1977 <dd>
1978 <p>
1979 non-matching text in selected lines
1980 </p>
1981 </dd>
1984 </dt>
1985 <dd>
1986 <p>
1989 </p>
1990 </dd>
1991 </dl></div>
1992 <div class="paragraph"><p>The values of these variables may be specified as in color.branch.<slot>.</p></div>
1993 </dd>
1995 color.interactive
1996 </dt>
1997 <dd>
1998 <p>
2000 and displays (such as those used by "git-add --interactive").
2002 colors only when the output is to the terminal. Defaults to false.
2003 </p>
2004 </dd>
2007 </dt>
2008 <dd>
2009 <p>
2011 output. <tt><slot></tt> may be <tt>prompt</tt>, <tt>header</tt>, <tt>help</tt> or <tt>error</tt>, for
2012 four distinct types of normal output from interactive
2013 commands. The values of these variables may be specified as
2015 </p>
2016 </dd>
2018 color.pager
2019 </dt>
2020 <dd>
2021 <p>
2022 A boolean to enable/disable colored output when the pager is in
2023 use (default is true).
2024 </p>
2025 </dd>
2027 color.showbranch
2028 </dt>
2029 <dd>
2030 <p>
2031 A boolean to enable/disable color in the output of
2033 <tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt> (or <tt>true</tt>), in which case colors are used
2034 only when the output is to a terminal. Defaults to false.
2035 </p>
2036 </dd>
2038 color.status
2039 </dt>
2040 <dd>
2041 <p>
2042 A boolean to enable/disable color in the output of
2044 <tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt> (or <tt>true</tt>), in which case colors are used
2045 only when the output is to a terminal. Defaults to false.
2046 </p>
2047 </dd>
2050 </dt>
2051 <dd>
2052 <p>
2060 to red). The values of these variables may be specified as in
2062 </p>
2063 </dd>
2065 color.ui
2066 </dt>
2067 <dd>
2068 <p>
2072 terminal. When more specific variables of color.* are set, they always
2073 take precedence over this setting. Defaults to false.
2074 </p>
2075 </dd>
2077 commit.status
2078 </dt>
2079 <dd>
2080 <p>
2081 A boolean to enable/disable inclusion of status information in the
2082 commit message template when using an editor to prepare the commit
2083 message. Defaults to true.
2084 </p>
2085 </dd>
2087 commit.template
2088 </dt>
2089 <dd>
2090 <p>
2091 Specify a file to use as the template for new commit messages.
2093 specified user’s home directory.
2094 </p>
2095 </dd>
2097 diff.autorefreshindex
2098 </dt>
2099 <dd>
2100 <p>
2102 files, do not consider stat-only change as changed.
2104 update the cached stat information for paths whose
2105 contents in the work tree match the contents in the
2106 index. This option defaults to true. Note that this
2109 </p>
2110 </dd>
2112 diff.external
2113 </dt>
2114 <dd>
2115 <p>
2116 If this config variable is set, diff generation is not
2117 performed using the internal diff machinery, but using the
2119 environment variable. The command is called with parameters
2121 you want to use an external diff program only on a subset of
2123 </p>
2124 </dd>
2126 diff.mnemonicprefix
2127 </dt>
2128 <dd>
2129 <p>
2132 this configuration is in effect, reverse diff output also swaps
2133 the order of the prefixes:
2134 </p>
2138 </dt>
2139 <dd>
2140 <p>
2141 compares the (i)ndex and the (w)ork tree;
2142 </p>
2143 </dd>
2146 </dt>
2147 <dd>
2148 <p>
2149 compares a (c)ommit and the (w)ork tree;
2150 </p>
2151 </dd>
2154 </dt>
2155 <dd>
2156 <p>
2157 compares a (c)ommit and the (i)ndex;
2158 </p>
2159 </dd>
2162 </dt>
2163 <dd>
2164 <p>
2165 compares an (o)bject and a (w)ork tree entity;
2166 </p>
2167 </dd>
2170 </dt>
2171 <dd>
2172 <p>
2174 </p>
2175 </dd>
2176 </dl></div>
2177 </dd>
2179 diff.noprefix
2180 </dt>
2181 <dd>
2182 <p>
2184 </p>
2185 </dd>
2187 diff.renameLimit
2188 </dt>
2189 <dd>
2190 <p>
2191 The number of files to consider when performing the copy/rename
2193 </p>
2194 </dd>
2196 diff.renames
2197 </dt>
2198 <dd>
2199 <p>
2200 Tells git to detect renames. If set to any boolean value, it
2201 will enable basic rename detection. If set to "copies" or
2202 "copy", it will detect copies, as well.
2203 </p>
2204 </dd>
2206 diff.ignoreSubmodules
2207 </dt>
2208 <dd>
2209 <p>
2210 Sets the default value of --ignore-submodules. Note that this
2213 this setting when reporting uncommitted changes.
2214 </p>
2215 </dd>
2217 diff.suppressBlankEmpty
2218 </dt>
2219 <dd>
2220 <p>
2221 A boolean to inhibit the standard behavior of printing a space
2222 before each empty output line. Defaults to false.
2223 </p>
2224 </dd>
2226 diff.tool
2227 </dt>
2228 <dd>
2229 <p>
2233 and plus "kompare".
2234 </p>
2235 </dd>
2238 </dt>
2239 <dd>
2240 <p>
2241 Override the path for the given tool. This is useful in case
2242 your tool is not in the PATH.
2243 </p>
2244 </dd>
2247 </dt>
2248 <dd>
2249 <p>
2250 Specify the command to invoke the specified diff tool.
2251 The specified command is evaluated in shell with the following
2254 is set to the name of the temporary file containing the contents
2255 of the diff post-image.
2256 </p>
2257 </dd>
2259 difftool.prompt
2260 </dt>
2261 <dd>
2262 <p>
2263 Prompt before each invocation of the diff tool.
2264 </p>
2265 </dd>
2267 diff.wordRegex
2268 </dt>
2269 <dd>
2270 <p>
2271 A POSIX Extended Regular Expression used to determine what is a "word"
2272 when performing word-by-word difference calculations. Character
2273 sequences that match the regular expression are "words", all other
2275 </p>
2276 </dd>
2278 fetch.recurseSubmodules
2279 </dt>
2280 <dd>
2281 <p>
2282 A boolean value which changes the behavior for fetch and pull, the
2283 default is to not recursively fetch populated submodules unless
2284 configured otherwise.
2285 </p>
2286 </dd>
2288 fetch.unpackLimit
2289 </dt>
2290 <dd>
2291 <p>
2292 If the number of objects fetched over the git native
2293 transfer is below this
2294 limit, then the objects will be unpacked into loose object
2295 files. However if the number of received objects equals or
2296 exceeds this limit then the received pack will be stored as
2297 a pack, after adding any missing delta bases. Storing the
2298 pack from a push can make the push operation complete faster,
2299 especially on slow filesystems. If not set, the value of
2301 </p>
2302 </dd>
2304 format.attach
2305 </dt>
2306 <dd>
2307 <p>
2308 Enable multipart/mixed attachments as the default for
2310 which will enable attachments as the default and set the
2311 value as the boundary. See the --attach option in
2313 </p>
2314 </dd>
2316 format.numbered
2317 </dt>
2318 <dd>
2319 <p>
2320 A boolean which can enable or disable sequence numbers in patch
2321 subjects. It defaults to "auto" which enables it only if there
2322 is more than one patch. It can be enabled or disabled for all
2325 </p>
2326 </dd>
2328 format.headers
2329 </dt>
2330 <dd>
2331 <p>
2332 Additional email headers to include in a patch to be submitted
2334 </p>
2335 </dd>
2337 format.to
2338 </dt>
2340 format.cc
2341 </dt>
2342 <dd>
2343 <p>
2344 Additional recipients to include in a patch to be submitted
2345 by mail. See the --to and --cc options in
2347 </p>
2348 </dd>
2350 format.subjectprefix
2351 </dt>
2352 <dd>
2353 <p>
2355 subject prefix. Use this variable to change that prefix.
2356 </p>
2357 </dd>
2359 format.signature
2360 </dt>
2361 <dd>
2362 <p>
2363 The default for format-patch is to output a signature containing
2364 the git version number. Use this variable to change that default.
2365 Set this variable to the empty string ("") to suppress
2366 signature generation.
2367 </p>
2368 </dd>
2370 format.suffix
2371 </dt>
2372 <dd>
2373 <p>
2374 The default for format-patch is to output files with the suffix
2376 include the dot if you want it).
2377 </p>
2378 </dd>
2380 format.pretty
2381 </dt>
2382 <dd>
2383 <p>
2384 The default pretty format for log/show/whatchanged command,
2387 </p>
2388 </dd>
2390 format.thread
2391 </dt>
2392 <dd>
2393 <p>
2396 makes every mail a reply to the head of the series,
2397 where the head is chosen from the cover letter, the
2401 value disables threading.
2402 </p>
2403 </dd>
2405 format.signoff
2406 </dt>
2407 <dd>
2408 <p>
2411 patch should be a conscious act and means that you certify you have
2412 the rights to submit this work under the same open source license.
2414 </p>
2415 </dd>
2417 gc.aggressiveWindow
2418 </dt>
2419 <dd>
2420 <p>
2421 The window size parameter used in the delta compression
2423 to 250.
2424 </p>
2425 </dd>
2427 gc.auto
2428 </dt>
2429 <dd>
2430 <p>
2431 When there are approximately more than this many loose
2433 Some Porcelain commands use this command to perform a
2434 light-weight garbage collection from time to time. The
2436 </p>
2437 </dd>
2439 gc.autopacklimit
2440 </dt>
2441 <dd>
2442 <p>
2443 When there are more than this many packs that are not
2445 --auto</tt> consolidates them into one larger pack. The
2447 </p>
2448 </dd>
2450 gc.packrefs
2451 </dt>
2452 <dd>
2453 <p>
2455 unclonable by Git versions prior to 1.5.1.2 over dumb
2456 transports such as HTTP. This variable determines whether
2458 to enable it within all non-bare repos or it can be set to a
2460 </p>
2461 </dd>
2463 gc.pruneexpire
2464 </dt>
2465 <dd>
2466 <p>
2468 Override the grace period with this config variable. The value
2469 "now" may be used to disable this grace period and always prune
2470 unreachable objects immediately.
2471 </p>
2472 </dd>
2474 gc.reflogexpire
2475 </dt>
2478 </dt>
2479 <dd>
2480 <p>
2483 "refs/stash") in the middle the setting applies only to
2485 </p>
2486 </dd>
2488 gc.reflogexpireunreachable
2489 </dt>
2492 </dt>
2493 <dd>
2494 <p>
2496 this time and are not reachable from the current tip;
2498 in the middle, the setting applies only to the refs that
2500 </p>
2501 </dd>
2503 gc.rerereresolved
2504 </dt>
2505 <dd>
2506 <p>
2507 Records of conflicted merge you resolved earlier are
2510 </p>
2511 </dd>
2513 gc.rerereunresolved
2514 </dt>
2515 <dd>
2516 <p>
2517 Records of conflicted merge you have not resolved are
2520 </p>
2521 </dd>
2523 gitcvs.commitmsgannotation
2524 </dt>
2525 <dd>
2526 <p>
2527 Append this string to each commit message. Set to empty string
2528 to disable this feature. Defaults to "via git-CVS emulator".
2529 </p>
2530 </dd>
2532 gitcvs.enabled
2533 </dt>
2534 <dd>
2535 <p>
2536 Whether the CVS server interface is enabled for this repository.
2538 </p>
2539 </dd>
2541 gitcvs.logfile
2542 </dt>
2543 <dd>
2544 <p>
2545 Path to a log file where the CVS server interface well… logs
2547 </p>
2548 </dd>
2550 gitcvs.usecrlfattr
2551 </dt>
2552 <dd>
2553 <p>
2554 If true, the server will look up the end-of-line conversion
2556 the attributes force git to treat a file as text,
2558 treat it as text. If they suppress text conversion, the file
2560 the client might otherwise do. If the attributes do not allow
2563 </p>
2564 </dd>
2566 gitcvs.allbinary
2567 </dt>
2568 <dd>
2569 <p>
2572 unresolved files are sent to the client in
2574 as binary files, which suppresses any newline munging it
2575 otherwise might do. Alternatively, if it is set to "guess",
2576 then the contents of the file are examined to decide if
2578 </p>
2579 </dd>
2581 gitcvs.dbname
2582 </dt>
2583 <dd>
2584 <p>
2585 Database used by git-cvsserver to cache revision information
2586 derived from the git repository. The exact meaning depends on the
2587 used database driver, for SQLite (which is the default driver) this
2588 is a filename. Supports variable substitution (see
2589 <a href="git-cvsserver.html">git-cvsserver(1)</a> for details). May not contain semicolons (<tt>;</tt>).
2591 </p>
2592 </dd>
2594 gitcvs.dbdriver
2595 </dt>
2596 <dd>
2597 <p>
2598 Used Perl DBI driver. You can specify any available driver
2599 for this here, but it might not work. git-cvsserver is tested
2604 </p>
2605 </dd>
2607 gitcvs.dbuser, gitcvs.dbpass
2608 </dt>
2609 <dd>
2610 <p>
2612 since SQLite has no concept of database users and/or passwords.
2615 </p>
2616 </dd>
2618 gitcvs.dbTableNamePrefix
2619 </dt>
2620 <dd>
2621 <p>
2622 Database table name prefix. Prepended to the names of any
2623 database tables used, allowing a single database to be used
2624 for several repositories. Supports variable substitution (see
2626 characters will be replaced with underscores.
2627 </p>
2628 </dd>
2629 </dl></div>
2634 access method.</p></div>
2637 gui.commitmsgwidth
2638 </dt>
2639 <dd>
2640 <p>
2641 Defines how wide the commit message window is in the
2643 </p>
2644 </dd>
2646 gui.diffcontext
2647 </dt>
2648 <dd>
2649 <p>
2650 Specifies how many context lines should be used in calls to diff
2652 </p>
2653 </dd>
2655 gui.encoding
2656 </dt>
2657 <dd>
2658 <p>
2659 Specifies the default encoding to use for displaying of
2663 If this option is not set, the tools default to the
2664 locale encoding.
2665 </p>
2666 </dd>
2668 gui.matchtrackingbranch
2669 </dt>
2670 <dd>
2671 <p>
2673 default to tracking remote branches with matching names or
2674 not. Default: "false".
2675 </p>
2676 </dd>
2678 gui.newbranchtemplate
2679 </dt>
2680 <dd>
2681 <p>
2682 Is used as suggested name when creating new branches using the
2684 </p>
2685 </dd>
2687 gui.pruneduringfetch
2688 </dt>
2689 <dd>
2690 <p>
2692 performing a fetch. The default value is "false".
2693 </p>
2694 </dd>
2696 gui.trustmtime
2697 </dt>
2698 <dd>
2699 <p>
2701 timestamp or not. By default the timestamps are not trusted.
2702 </p>
2703 </dd>
2705 gui.spellingdictionary
2706 </dt>
2707 <dd>
2708 <p>
2709 Specifies the dictionary used for spell checking commit messages in
2711 off.
2712 </p>
2713 </dd>
2715 gui.fastcopyblame
2716 </dt>
2717 <dd>
2718 <p>
2720 location detection. It makes blame significantly faster on huge
2721 repositories at the expense of less thorough copy detection.
2722 </p>
2723 </dd>
2725 gui.copyblamethreshold
2726 </dt>
2727 <dd>
2728 <p>
2730 detection, measured in alphanumeric characters. See the
2732 </p>
2733 </dd>
2735 gui.blamehistoryctx
2736 </dt>
2737 <dd>
2738 <p>
2739 Specifies the radius of history context in days to show in
2742 variable is set to zero, the whole history is shown.
2743 </p>
2744 </dd>
2747 </dt>
2748 <dd>
2749 <p>
2750 Specifies the shell command line to execute when the corresponding item
2752 mandatory for every tool. The command is executed from the root of
2753 the working directory, and in the environment it receives the name of
2757 </p>
2758 </dd>
2761 </dt>
2762 <dd>
2763 <p>
2764 Run the tool only if a diff is selected in the GUI. It guarantees
2766 </p>
2767 </dd>
2770 </dt>
2771 <dd>
2772 <p>
2773 Run the command silently, without creating a window to display its
2774 output.
2775 </p>
2776 </dd>
2779 </dt>
2780 <dd>
2781 <p>
2782 Don’t rescan the working directory for changes after the tool
2783 finishes execution.
2784 </p>
2785 </dd>
2788 </dt>
2789 <dd>
2790 <p>
2791 Show a confirmation dialog before actually running the tool.
2792 </p>
2793 </dd>
2796 </dt>
2797 <dd>
2798 <p>
2799 Request a string argument from the user, and pass it to the tool
2803 the dialog uses a built-in generic prompt; otherwise the exact
2804 value of the variable is used.
2805 </p>
2806 </dd>
2809 </dt>
2810 <dd>
2811 <p>
2812 Request a single valid revision from the user, and set the
2815 </p>
2816 </dd>
2819 </dt>
2820 <dd>
2821 <p>
2823 This is useful for tools similar to merge or rebase, but not
2824 for things like checkout or reset.
2825 </p>
2826 </dd>
2829 </dt>
2830 <dd>
2831 <p>
2832 Specifies the title to use for the prompt dialog. The default
2833 is the tool name.
2834 </p>
2835 </dd>
2838 </dt>
2839 <dd>
2840 <p>
2841 Specifies the general prompt string to display at the top of
2843 The default value includes the actual command.
2844 </p>
2845 </dd>
2847 help.browser
2848 </dt>
2849 <dd>
2850 <p>
2851 Specify the browser that will be used to display help in the
2853 </p>
2854 </dd>
2856 help.format
2857 </dt>
2858 <dd>
2859 <p>
2861 Values <em>man</em>, <em>info</em>, <em>web</em> and <em>html</em> are supported. <em>man</em> is
2863 </p>
2864 </dd>
2866 help.autocorrect
2867 </dt>
2868 <dd>
2869 <p>
2870 Automatically correct and execute mistyped commands after
2871 waiting for the given number of deciseconds (0.1 sec). If more
2872 than one command can be deduced from the entered text, nothing
2873 will be executed. If the value of this option is negative,
2874 the corrected command will be executed immediately. If the
2875 value is 0 - the command will be just shown but not executed.
2876 This is the default.
2877 </p>
2878 </dd>
2880 http.proxy
2881 </dt>
2882 <dd>
2883 <p>
2887 </p>
2888 </dd>
2890 http.sslVerify
2891 </dt>
2892 <dd>
2893 <p>
2894 Whether to verify the SSL certificate when fetching or pushing
2896 variable.
2897 </p>
2898 </dd>
2900 http.sslCert
2901 </dt>
2902 <dd>
2903 <p>
2904 File containing the SSL certificate when fetching or pushing
2906 variable.
2907 </p>
2908 </dd>
2910 http.sslKey
2911 </dt>
2912 <dd>
2913 <p>
2914 File containing the SSL private key when fetching or pushing
2916 variable.
2917 </p>
2918 </dd>
2920 http.sslCertPasswordProtected
2921 </dt>
2922 <dd>
2923 <p>
2924 Enable git’s password prompt for the SSL certificate. Otherwise
2925 OpenSSL will prompt the user, possibly many times, if the
2926 certificate or private key is encrypted. Can be overridden by the
2928 </p>
2929 </dd>
2931 http.sslCAInfo
2932 </dt>
2933 <dd>
2934 <p>
2935 File containing the certificates to verify the peer with when
2936 fetching or pushing over HTTPS. Can be overridden by the
2938 </p>
2939 </dd>
2941 http.sslCAPath
2942 </dt>
2943 <dd>
2944 <p>
2945 Path containing files with the CA certificates to verify the peer
2946 with when fetching or pushing over HTTPS. Can be overridden
2948 </p>
2949 </dd>
2951 http.maxRequests
2952 </dt>
2953 <dd>
2954 <p>
2955 How many HTTP requests to launch in parallel. Can be overridden
2957 </p>
2958 </dd>
2960 http.minSessions
2961 </dt>
2962 <dd>
2963 <p>
2964 The number of curl sessions (counted across slots) to be kept across
2965 requests. They will not be ended with curl_easy_cleanup() until
2966 http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this
2968 </p>
2969 </dd>
2971 http.postBuffer
2972 </dt>
2973 <dd>
2974 <p>
2975 Maximum size in bytes of the buffer used by smart HTTP
2976 transports when POSTing data to the remote system.
2977 For requests larger than this buffer size, HTTP/1.1 and
2978 Transfer-Encoding: chunked is used to avoid creating a
2979 massive pack file locally. Default is 1 MiB, which is
2980 sufficient for most requests.
2981 </p>
2982 </dd>
2984 http.lowSpeedLimit, http.lowSpeedTime
2985 </dt>
2986 <dd>
2987 <p>
2992 </p>
2993 </dd>
2995 http.noEPSV
2996 </dt>
2997 <dd>
2998 <p>
2999 A boolean which disables using of EPSV ftp command by curl.
3002 environment variable. Default is false (curl will use EPSV).
3003 </p>
3004 </dd>
3006 http.useragent
3007 </dt>
3008 <dd>
3009 <p>
3010 The HTTP USER_AGENT string presented to an HTTP server. The default
3011 value represents the version of the client git such as git/1.7.1.
3012 This option allows you to override this value to a more common value
3013 such as Mozilla/4.0. This may be necessary, for instance, if
3014 connecting through a firewall that restricts HTTP connections to a set
3015 of common USER_AGENT strings (but not including those like git/1.7.1).
3017 </p>
3018 </dd>
3020 i18n.commitEncoding
3021 </dt>
3022 <dd>
3023 <p>
3024 Character encoding the commit messages are stored in; git itself
3025 does not care per se, but this information is necessary e.g. when
3026 importing commits from emails or in the gitk graphical history
3027 browser (and possibly at other places in the future or in other
3028 porcelains). See e.g. <a href="git-mailinfo.html">git-mailinfo(1)</a>. Defaults to <em>utf-8</em>.
3029 </p>
3030 </dd>
3032 i18n.logOutputEncoding
3033 </dt>
3034 <dd>
3035 <p>
3036 Character encoding the commit messages are converted to when
3038 </p>
3039 </dd>
3041 imap
3042 </dt>
3043 <dd>
3044 <p>
3047 </p>
3048 </dd>
3050 init.templatedir
3051 </dt>
3052 <dd>
3053 <p>
3054 Specify the directory from which templates will be copied.
3056 </p>
3057 </dd>
3059 instaweb.browser
3060 </dt>
3061 <dd>
3062 <p>
3063 Specify the program that will be used to browse your working
3065 </p>
3066 </dd>
3068 instaweb.httpd
3069 </dt>
3070 <dd>
3071 <p>
3072 The HTTP daemon command-line to start gitweb on your working
3074 </p>
3075 </dd>
3077 instaweb.local
3078 </dt>
3079 <dd>
3080 <p>
3082 be bound to the local IP (127.0.0.1).
3083 </p>
3084 </dd>
3086 instaweb.modulepath
3087 </dt>
3088 <dd>
3089 <p>
3091 instead of /usr/lib/apache2/modules. Only used if httpd
3092 is Apache.
3093 </p>
3094 </dd>
3096 instaweb.port
3097 </dt>
3098 <dd>
3099 <p>
3100 The port number to bind the gitweb httpd to. See
3102 </p>
3103 </dd>
3105 interactive.singlekey
3106 </dt>
3107 <dd>
3108 <p>
3109 In interactive commands, allow the user to provide one-letter
3110 input with a single key (i.e., without hitting enter).
3113 ignored if portable keystroke input is not available.
3114 </p>
3115 </dd>
3117 log.date
3118 </dt>
3119 <dd>
3120 <p>
3124 <tt>default</tt>, <tt>iso</tt>, <tt>rfc</tt>, and <tt>short</tt>; see <a href="git-log.html">git-log(1)</a>
3125 for details.
3126 </p>
3127 </dd>
3129 log.decorate
3130 </dt>
3131 <dd>
3132 <p>
3133 Print out the ref names of any commits that are shown by the log
3136 specified, the full ref name (including prefix) will be printed.
3138 </p>
3139 </dd>
3141 log.showroot
3142 </dt>
3143 <dd>
3144 <p>
3145 If true, the initial commit will be shown as a big creation event.
3146 This is equivalent to a diff against an empty tree.
3147 Tools like <a href="git-log.html">git-log(1)</a> or <a href="git-whatchanged.html">git-whatchanged(1)</a>, which
3148 normally hide the root commit will now show it. True by default.
3149 </p>
3150 </dd>
3152 mailmap.file
3153 </dt>
3154 <dd>
3155 <p>
3156 The location of an augmenting mailmap file. The default
3157 mailmap, located in the root of the repository, is loaded
3158 first, then the mailmap file pointed to by this variable.
3159 The location of the mailmap file may be in a repository
3160 subdirectory, or somewhere outside of the repository itself.
3161 See <a href="git-shortlog.html">git-shortlog(1)</a> and <a href="git-blame.html">git-blame(1)</a>.
3162 </p>
3163 </dd>
3165 man.viewer
3166 </dt>
3167 <dd>
3168 <p>
3169 Specify the programs that may be used to display help in the
3171 </p>
3172 </dd>
3175 </dt>
3176 <dd>
3177 <p>
3178 Specify the command to invoke the specified man viewer. The
3179 specified command is evaluated in shell with the man page
3181 </p>
3182 </dd>
3185 </dt>
3186 <dd>
3187 <p>
3188 Override the path for the given tool that may be used to
3190 </p>
3191 </dd>
3193 merge.conflictstyle
3194 </dt>
3195 <dd>
3196 <p>
3197 Specify the style in which conflicted hunks are written out to
3198 working tree files upon merge. The default is "merge", which
3201 a <tt>>>>>>>></tt> marker. An alternate style, "diff3", adds a <tt>|||||||</tt>
3203 </p>
3204 </dd>
3206 merge.log
3207 </dt>
3208 <dd>
3209 <p>
3210 In addition to branch names, populate the log message with at
3211 most the specified number of one-line descriptions from the
3212 actual commits that are being merged. Defaults to false, and
3213 true is a synonym for 20.
3214 </p>
3215 </dd>
3217 merge.renameLimit
3218 </dt>
3219 <dd>
3220 <p>
3221 The number of files to consider when performing rename detection
3222 during a merge; if not specified, defaults to the value of
3223 diff.renameLimit.
3224 </p>
3225 </dd>
3227 merge.renormalize
3228 </dt>
3229 <dd>
3230 <p>
3231 Tell git that canonical representation of files in the
3232 repository has changed over time (e.g. earlier commits record
3233 text files with CRLF line endings, but recent ones use LF line
3234 endings). In such a repository, git can convert the data
3235 recorded in commits to a canonical form before performing a
3236 merge to reduce unnecessary conflicts. For more information,
3237 see section "Merging branches with differing checkin/checkout
3239 </p>
3240 </dd>
3242 merge.stat
3243 </dt>
3244 <dd>
3245 <p>
3246 Whether to print the diffstat between ORIG_HEAD and the merge result
3247 at the end of the merge. True by default.
3248 </p>
3249 </dd>
3251 merge.tool
3252 </dt>
3253 <dd>
3254 <p>
3255 Controls which merge resolution program is used by
3259 "opendiff". Any other value is treated is custom merge tool
3261 </p>
3262 </dd>
3264 merge.verbosity
3265 </dt>
3266 <dd>
3267 <p>
3268 Controls the amount of output shown by the recursive merge
3269 strategy. Level 0 outputs nothing except a final error
3270 message if conflicts were detected. Level 1 outputs only
3272 above outputs debugging information. The default is level 2.
3274 </p>
3275 </dd>
3278 </dt>
3279 <dd>
3280 <p>
3281 Defines a human-readable name for a custom low-level
3283 </p>
3284 </dd>
3287 </dt>
3288 <dd>
3289 <p>
3290 Defines the command that implements a custom low-level
3292 </p>
3293 </dd>
3296 </dt>
3297 <dd>
3298 <p>
3299 Names a low-level merge driver to be used when
3300 performing an internal merge between common ancestors.
3302 </p>
3303 </dd>
3306 </dt>
3307 <dd>
3308 <p>
3309 Override the path for the given tool. This is useful in case
3310 your tool is not in the PATH.
3311 </p>
3312 </dd>
3315 </dt>
3316 <dd>
3317 <p>
3318 Specify the command to invoke the specified merge tool. The
3319 specified command is evaluated in shell with the following
3321 containing the common base of the files to be merged, if available;
3324 file containing the contents of the file from the branch being
3326 tool should write the results of a successful merge.
3327 </p>
3328 </dd>
3331 </dt>
3332 <dd>
3333 <p>
3334 For a custom merge command, specify whether the exit code of
3335 the merge command can be used to determine whether the merge was
3336 successful. If this is not set to true then the merge target file
3337 timestamp is checked and the merge assumed to have been successful
3338 if the file has been updated, otherwise the user is prompted to
3339 indicate the success of the merge.
3340 </p>
3341 </dd>
3343 mergetool.keepBackup
3344 </dt>
3345 <dd>
3346 <p>
3347 After performing a merge, the original file with conflict markers
3351 </p>
3352 </dd>
3354 mergetool.keepTemporaries
3355 </dt>
3356 <dd>
3357 <p>
3358 When invoking a custom merge tool, git uses a set of temporary
3359 files to pass to the tool. If the tool returns an error and this
3361 preserved, otherwise they will be removed after the tool has
3363 </p>
3364 </dd>
3366 mergetool.prompt
3367 </dt>
3368 <dd>
3369 <p>
3370 Prompt before each invocation of the merge resolution program.
3371 </p>
3372 </dd>
3374 notes.displayRef
3375 </dt>
3376 <dd>
3377 <p>
3378 The (fully qualified) refname from which to show notes when
3379 showing commit messages. The value of this variable can be set
3380 to a glob, in which case notes from all matching refs will be
3381 shown. You may also specify this configuration variable
3382 several times. A warning will be issued for refs that do not
3383 exist, but a glob that does not match any refs is silently
3384 ignored.
3385 </p>
3386 <div class="paragraph"><p>This setting can be overridden with the <tt>GIT_NOTES_DISPLAY_REF</tt>
3387 environment variable, which must be a colon separated list of refs or
3388 globs.</p></div>
3390 GIT_NOTES_REF) is also implicitly added to the list of refs to be
3391 displayed.</p></div>
3392 </dd>
3395 </dt>
3396 <dd>
3397 <p>
3400 automatically copies your notes from the original to the
3402 "notes.rewriteRef" below.
3403 </p>
3404 </dd>
3406 notes.rewriteMode
3407 </dt>
3408 <dd>
3409 <p>
3410 When copying notes during a rewrite (see the
3411 "notes.rewrite.<command>" option), determines what to do if
3412 the target commit already has a note. Must be one of
3415 </p>
3416 <div class="paragraph"><p>This setting can be overridden with the <tt>GIT_NOTES_REWRITE_MODE</tt>
3417 environment variable.</p></div>
3418 </dd>
3420 notes.rewriteRef
3421 </dt>
3422 <dd>
3423 <p>
3424 When copying notes during a rewrite, specifies the (fully
3425 qualified) ref whose notes should be copied. The ref may be a
3426 glob, in which case notes in all matching refs will be copied.
3427 You may also specify this configuration several times.
3428 </p>
3430 enable note rewriting.</p></div>
3431 <div class="paragraph"><p>This setting can be overridden with the <tt>GIT_NOTES_REWRITE_REF</tt>
3432 environment variable, which must be a colon separated list of refs or
3433 globs.</p></div>
3434 </dd>
3436 pack.window
3437 </dt>
3438 <dd>
3439 <p>
3441 window size is given on the command line. Defaults to 10.
3442 </p>
3443 </dd>
3445 pack.depth
3446 </dt>
3447 <dd>
3448 <p>
3449 The maximum delta depth used by <a href="git-pack-objects.html">git-pack-objects(1)</a> when no
3450 maximum depth is given on the command line. Defaults to 50.
3451 </p>
3452 </dd>
3454 pack.windowMemory
3455 </dt>
3456 <dd>
3457 <p>
3459 when no limit is given on the command line. The value can be
3461 limit.
3462 </p>
3463 </dd>
3465 pack.compression
3466 </dt>
3467 <dd>
3468 <p>
3472 slowest. If not set, defaults to core.compression. If that is
3474 compromise between speed and compression (currently equivalent
3475 to level 6)."
3476 </p>
3477 <div class="paragraph"><p>Note that changing the compression level will not automatically recompress
3478 all existing objects. You can force recompression by passing the -F option
3480 </dd>
3482 pack.deltaCacheSize
3483 </dt>
3484 <dd>
3485 <p>
3486 The maximum memory in bytes used for caching deltas in
3488 This cache is used to speed up the writing object phase by not
3489 having to recompute the final delta result once the best match
3490 for all objects is found. Repacking large repositories on machines
3491 which are tight with memory might be badly impacted by this though,
3492 especially if this cache pushes the system into swapping.
3494 used to virtually disable this cache. Defaults to 256 MiB.
3495 </p>
3496 </dd>
3498 pack.deltaCacheLimit
3499 </dt>
3500 <dd>
3501 <p>
3502 The maximum size of a delta, that is cached in
3504 writing object phase by not having to recompute the final delta
3505 result once the best match for all objects is found. Defaults to 1000.
3506 </p>
3507 </dd>
3509 pack.threads
3510 </dt>
3511 <dd>
3512 <p>
3513 Specifies the number of threads to spawn when searching for best
3515 be compiled with pthreads otherwise this option is ignored with a
3516 warning. This is meant to reduce packing time on multiprocessor
3517 machines. The required amount of memory for the delta search window
3518 is however multiplied by the number of threads.
3520 and set the number of threads accordingly.
3521 </p>
3522 </dd>
3524 pack.indexVersion
3525 </dt>
3526 <dd>
3527 <p>
3528 Specify the default pack index version. Valid values are 1 for
3530 the new pack index with capabilities for packs larger than 4 GB
3531 as well as proper protection against the repacking of corrupted
3533 and this config option ignored whenever the corresponding pack is
3534 larger than 2 GB.
3535 </p>
3536 <div class="paragraph"><p>If you have an old git that does not understand the version 2 <tt>*.idx</tt> file,
3538 that will copy both <tt>*.pack</tt> file and corresponding <tt>*.idx</tt> file from the
3539 other side may give you a repository that cannot be accessed with your
3541 you can use <a href="git-index-pack.html">git-index-pack(1)</a> on the *.pack file to regenerate
3543 </dd>
3545 pack.packSizeLimit
3546 </dt>
3547 <dd>
3548 <p>
3549 The maximum size of a pack. This setting only affects
3550 packing to a file when repacking, i.e. the git:// protocol
3553 limited to 1 MiB. The default is unlimited.
3555 supported.
3556 </p>
3557 </dd>
3560 </dt>
3561 <dd>
3562 <p>
3563 If the value is boolean, turns on or off pagination of the
3564 output of a particular git subcommand when writing to a tty.
3565 Otherwise, turns on pagination for the subcommand using the
3568 precedence over this option. To disable pagination for all
3570 </p>
3571 </dd>
3574 </dt>
3575 <dd>
3576 <p>
3577 Alias for a --pretty= format string, as specified in
3579 as the built-in pretty formats could. For example,
3583 Note that an alias with the same name as a built-in format
3584 will be silently ignored.
3585 </p>
3586 </dd>
3588 pull.octopus
3589 </dt>
3590 <dd>
3591 <p>
3592 The default merge strategy to use when pulling multiple branches
3593 at once.
3594 </p>
3595 </dd>
3597 pull.twohead
3598 </dt>
3599 <dd>
3600 <p>
3601 The default merge strategy to use when pulling a single branch.
3602 </p>
3603 </dd>
3605 push.default
3606 </dt>
3607 <dd>
3608 <p>
3609 Defines the action git push should take if no refspec is given
3610 on the command line, no refspec is configured in the remote, and
3611 no refspec is implied by any of the options given on the command
3612 line. Possible values are:
3613 </p>
3615 <li>
3616 <p>
3618 </p>
3619 </li>
3620 <li>
3621 <p>
3623 All branches having the same name in both ends are considered to be
3624 matching. This is the default.
3625 </p>
3626 </li>
3627 <li>
3628 <p>
3630 </p>
3631 </li>
3632 <li>
3633 <p>
3635 </p>
3636 </li>
3637 </ul></div>
3638 </dd>
3640 rebase.stat
3641 </dt>
3642 <dd>
3643 <p>
3644 Whether to show a diffstat of what changed upstream since the last
3645 rebase. False by default.
3646 </p>
3647 </dd>
3649 rebase.autosquash
3650 </dt>
3651 <dd>
3652 <p>
3654 </p>
3655 </dd>
3657 receive.autogc
3658 </dt>
3659 <dd>
3660 <p>
3661 By default, git-receive-pack will run "git-gc --auto" after
3662 receiving data from git-push and updating refs. You can stop
3663 it by setting this variable to false.
3664 </p>
3665 </dd>
3667 receive.fsckObjects
3668 </dt>
3669 <dd>
3670 <p>
3671 If it is set to true, git-receive-pack will check all received
3672 objects. It will abort in the case of a malformed object or a
3673 broken link. The result of an abort are only dangling objects.
3674 Defaults to false.
3675 </p>
3676 </dd>
3678 receive.unpackLimit
3679 </dt>
3680 <dd>
3681 <p>
3682 If the number of objects received in a push is below this
3683 limit then the objects will be unpacked into loose object
3684 files. However if the number of received objects equals or
3685 exceeds this limit then the received pack will be stored as
3686 a pack, after adding any missing delta bases. Storing the
3687 pack from a push can make the push operation complete faster,
3688 especially on slow filesystems. If not set, the value of
3690 </p>
3691 </dd>
3693 receive.denyDeletes
3694 </dt>
3695 <dd>
3696 <p>
3697 If set to true, git-receive-pack will deny a ref update that deletes
3698 the ref. Use this to prevent such a ref deletion via a push.
3699 </p>
3700 </dd>
3702 receive.denyDeleteCurrent
3703 </dt>
3704 <dd>
3705 <p>
3706 If set to true, git-receive-pack will deny a ref update that
3707 deletes the currently checked out branch of a non-bare repository.
3708 </p>
3709 </dd>
3711 receive.denyCurrentBranch
3712 </dt>
3713 <dd>
3714 <p>
3715 If set to true or "refuse", git-receive-pack will deny a ref update
3716 to the currently checked out branch of a non-bare repository.
3717 Such a push is potentially dangerous because it brings the HEAD
3718 out of sync with the index and working tree. If set to "warn",
3719 print a warning of such a push to stderr, but allow the push to
3720 proceed. If set to false or "ignore", allow such pushes with no
3721 message. Defaults to "refuse".
3722 </p>
3723 </dd>
3725 receive.denyNonFastForwards
3726 </dt>
3727 <dd>
3728 <p>
3729 If set to true, git-receive-pack will deny a ref update which is
3730 not a fast-forward. Use this to prevent such an update via a push,
3731 even if that push is forced. This configuration variable is
3732 set when initializing a shared repository.
3733 </p>
3734 </dd>
3736 receive.updateserverinfo
3737 </dt>
3738 <dd>
3739 <p>
3740 If set to true, git-receive-pack will run git-update-server-info
3741 after receiving data from git-push and updating refs.
3742 </p>
3743 </dd>
3746 </dt>
3747 <dd>
3748 <p>
3751 </p>
3752 </dd>
3755 </dt>
3756 <dd>
3757 <p>
3759 </p>
3760 </dd>
3763 </dt>
3764 <dd>
3765 <p>
3766 For remotes that require curl (http, https and ftp), the URL to
3767 the proxy to use for that remote. Set to the empty string to
3768 disable proxying for that remote.
3769 </p>
3770 </dd>
3773 </dt>
3774 <dd>
3775 <p>
3778 </p>
3779 </dd>
3782 </dt>
3783 <dd>
3784 <p>
3787 </p>
3788 </dd>
3791 </dt>
3792 <dd>
3793 <p>
3794 If true, pushing to this remote will automatically behave
3796 </p>
3797 </dd>
3800 </dt>
3801 <dd>
3802 <p>
3803 If true, this remote will be skipped by default when updating
3806 </p>
3807 </dd>
3810 </dt>
3811 <dd>
3812 <p>
3813 If true, this remote will be skipped by default when updating
3816 </p>
3817 </dd>
3820 </dt>
3821 <dd>
3822 <p>
3823 The default program to execute on the remote side when pushing. See
3825 </p>
3826 </dd>
3829 </dt>
3830 <dd>
3831 <p>
3832 The default program to execute on the remote side when fetching. See
3834 </p>
3835 </dd>
3838 </dt>
3839 <dd>
3840 <p>
3841 Setting this value to --no-tags disables automatic tag following when
3845 override this setting. See options --tags and --no-tags of
3847 </p>
3848 </dd>
3851 </dt>
3852 <dd>
3853 <p>
3856 </p>
3857 </dd>
3860 </dt>
3861 <dd>
3862 <p>
3863 The list of remotes which are fetched by "git remote update
3865 </p>
3866 </dd>
3868 repack.usedeltabaseoffset
3869 </dt>
3870 <dd>
3871 <p>
3873 delta-base offset. If you need to share your repository with
3874 git older than version 1.4.4, either directly or via a dumb
3875 protocol such as http, then you need to set this option to
3876 "false" and repack. Access from old git versions over the
3877 native protocol are unaffected by this option.
3878 </p>
3879 </dd>
3881 rerere.autoupdate
3882 </dt>
3883 <dd>
3884 <p>
3886 resulting contents after it cleanly resolves conflicts using
3887 previously recorded resolution. Defaults to false.
3888 </p>
3889 </dd>
3891 rerere.enabled
3892 </dt>
3893 <dd>
3894 <p>
3895 Activate recording of resolved conflicts, so that identical
3896 conflict hunks can be resolved automatically, should they
3900 </p>
3901 </dd>
3903 sendemail.identity
3904 </dt>
3905 <dd>
3906 <p>
3907 A configuration identity. When given, causes values in the
3911 </p>
3912 </dd>
3914 sendemail.smtpencryption
3915 </dt>
3916 <dd>
3917 <p>
3920 </p>
3921 </dd>
3923 sendemail.smtpssl
3924 </dt>
3925 <dd>
3926 <p>
3928 </p>
3929 </dd>
3932 </dt>
3933 <dd>
3934 <p>
3936 found below, taking precedence over those when the this
3937 identity is selected, through command-line or
3939 </p>
3940 </dd>
3942 sendemail.aliasesfile
3943 </dt>
3945 sendemail.aliasfiletype
3946 </dt>
3948 sendemail.bcc
3949 </dt>
3951 sendemail.cc
3952 </dt>
3954 sendemail.cccmd
3955 </dt>
3957 sendemail.chainreplyto
3958 </dt>
3960 sendemail.confirm
3961 </dt>
3963 sendemail.envelopesender
3964 </dt>
3966 sendemail.from
3967 </dt>
3969 sendemail.multiedit
3970 </dt>
3972 sendemail.signedoffbycc
3973 </dt>
3975 sendemail.smtppass
3976 </dt>
3978 sendemail.suppresscc
3979 </dt>
3981 sendemail.suppressfrom
3982 </dt>
3984 sendemail.to
3985 </dt>
3987 sendemail.smtpdomain
3988 </dt>
3990 sendemail.smtpserver
3991 </dt>
3993 sendemail.smtpserverport
3994 </dt>
3996 sendemail.smtpserveroption
3997 </dt>
3999 sendemail.smtpuser
4000 </dt>
4002 sendemail.thread
4003 </dt>
4005 sendemail.validate
4006 </dt>
4007 <dd>
4008 <p>
4010 </p>
4011 </dd>
4013 sendemail.signedoffcc
4014 </dt>
4015 <dd>
4016 <p>
4018 </p>
4019 </dd>
4021 showbranch.default
4022 </dt>
4023 <dd>
4024 <p>
4027 </p>
4028 </dd>
4030 status.relativePaths
4031 </dt>
4032 <dd>
4033 <p>
4036 relative to the repository root (this was the default for git
4037 prior to v1.5.4).
4038 </p>
4039 </dd>
4041 status.showUntrackedFiles
4042 </dt>
4043 <dd>
4044 <p>
4045 By default, <a href="git-status.html">git-status(1)</a> and <a href="git-commit.html">git-commit(1)</a> show
4046 files which are not currently tracked by Git. Directories which
4047 contain only untracked files, are shown with the directory name
4048 only. Showing untracked files means that Git needs to lstat() all
4049 all the files in the whole repository, which might be slow on some
4050 systems. So, this variable controls how the commands displays
4051 the untracked files. Possible values are:
4052 </p>
4054 <li>
4055 <p>
4057 </p>
4058 </li>
4059 <li>
4060 <p>
4062 </p>
4063 </li>
4064 <li>
4065 <p>
4067 </p>
4068 </li>
4069 </ul></div>
4071 This variable can be overridden with the -u|--untracked-files option
4072 of <a href="git-status.html">git-status(1)</a> and <a href="git-commit.html">git-commit(1)</a>.</p></div>
4073 </dd>
4075 status.submodulesummary
4076 </dt>
4077 <dd>
4078 <p>
4079 Defaults to false.
4080 If this is set to a non zero number or true (identical to -1 or an
4081 unlimited number), the submodule summary will be enabled and a
4082 summary of commits for modified submodules will be shown (see
4084 </p>
4085 </dd>
4088 </dt>
4091 </dt>
4094 </dt>
4095 <dd>
4096 <p>
4097 The path within this project, URL, and the updating strategy
4098 for a submodule. These variables are initially populated
4101 <a href="git-submodule.html">git-submodule(1)</a> and <a href="gitmodules.html">gitmodules(5)</a> for details.
4102 </p>
4103 </dd>
4106 </dt>
4107 <dd>
4108 <p>
4109 This option can be used to enable/disable recursive fetching of this
4110 submodule. It can be overridden by using the --[no-]recurse-submodules
4113 file.
4114 </p>
4115 </dd>
4118 </dt>
4119 <dd>
4120 <p>
4121 Defines under what circumstances "git status" and the diff family show
4122 a submodule as modified. When set to "all", it will never be considered
4123 modified, "dirty" will ignore all changes to the submodules work tree and
4124 takes only differences between the HEAD of the submodule and the commit
4125 recorded in the superproject into account. "untracked" will additionally
4126 let submodules with modified tracked files in their work tree show up.
4127 Using "none" (the default when this option is not set) also shows
4128 submodules that have untracked files in their work tree as changed.
4129 This setting overrides any setting made in .gitmodules for this submodule,
4130 both settings can be overridden on the command line by using the
4131 "--ignore-submodules" option.
4132 </p>
4133 </dd>
4135 tar.umask
4136 </dt>
4137 <dd>
4138 <p>
4139 This variable can be used to restrict the permission bits of
4140 tar archive entries. The default is 0002, which turns off the
4141 world write bit. The special value "user" indicates that the
4144 </p>
4145 </dd>
4147 transfer.unpackLimit
4148 </dt>
4149 <dd>
4150 <p>
4152 not set, the value of this variable is used instead.
4153 The default value is 100.
4154 </p>
4155 </dd>
4158 </dt>
4159 <dd>
4160 <p>
4161 Any URL that starts with this value will be rewritten to
4163 large number of repositories, and serves them with multiple
4164 access methods, and some users need to use different access
4165 methods, this feature allows people to specify any of the
4166 equivalent URLs and have git automatically rewrite the URL to
4167 the best alternative for the particular user, even for a
4168 never-before-seen repository on the site. When more than one
4169 insteadOf strings match a given URL, the longest match is used.
4170 </p>
4171 </dd>
4174 </dt>
4175 <dd>
4176 <p>
4177 Any URL that starts with this value will not be pushed to;
4179 resulting URL will be pushed to. In cases where some site serves
4180 a large number of repositories, and serves them with multiple
4181 access methods, some of which do not allow push, this feature
4182 allows people to specify a pull-only URL and have git
4183 automatically use an appropriate URL to push, even for a
4184 never-before-seen repository on the site. When more than one
4185 pushInsteadOf strings match a given URL, the longest match is
4186 used. If a remote has an explicit pushurl, git will ignore this
4187 setting for that remote.
4188 </p>
4189 </dd>
4191 user.email
4192 </dt>
4193 <dd>
4194 <p>
4195 Your email address to be recorded in any newly created commits.
4197 <em>EMAIL</em> environment variables. See <a href="git-commit-tree.html">git-commit-tree(1)</a>.
4198 </p>
4199 </dd>
4201 user.name
4202 </dt>
4203 <dd>
4204 <p>
4205 Your full name to be recorded in any newly created commits.
4208 </p>
4209 </dd>
4211 user.signingkey
4212 </dt>
4213 <dd>
4214 <p>
4216 automatically when creating a signed tag, you can override the
4217 default selection with this variable. This option is passed
4218 unchanged to gpg’s --local-user parameter, so you may specify a key
4219 using any method that gpg supports.
4220 </p>
4221 </dd>
4223 web.browser
4224 </dt>
4225 <dd>
4226 <p>
4227 Specify a web browser that may be used by some commands.
4228 Currently only <a href="git-instaweb.html">git-instaweb(1)</a> and <a href="git-help.html">git-help(1)</a>
4229 may use it.
4230 </p>
4231 </dd>
4232 </dl></div>
4233 </div>
4236 <div class="paragraph"><p>Written by Johannes Schindelin <<a href="mailto:Johannes.Schindelin@gmx.de">Johannes.Schindelin@gmx.de</a>></p></div>
4237 </div>
4240 <div class="paragraph"><p>Documentation by Johannes Schindelin, Petr Baudis and the git-list <<a href="mailto:git@vger.kernel.org">git@vger.kernel.org</a>>.</p></div>
4241 </div>
4245 </div>
4249 </div>
4250 </div>
4251 </body>
4252 </html>