| blob | c1c793972624dc9c3b2276f35c993036fac35b6f |
4 <head>
8 /* Debug borders */
10 /*
11 border: 1px solid red;
12 */
13 }
15 body {
17 }
19 a {
22 }
25 }
27 em {
29 }
31 strong {
33 }
35 tt {
37 }
45 }
49 }
50 h2 {
52 }
53 h3 {
55 }
56 h3 + * {
58 }
63 }
65 hr {
67 }
69 p {
72 }
74 pre {
77 }
79 span#author {
84 }
85 span#email {
86 }
87 span#revision {
89 }
91 div#footer {
97 }
98 div#footer-text {
101 }
102 div#footer-badges {
105 }
107 div#preamble,
114 }
118 }
122 }
124 /* Block element titles. */
131 }
134 }
138 }
141 }
144 }
150 }
154 }
159 }
163 }
167 }
170 }
179 }
183 }
188 }
192 }
198 dl {
201 }
202 dt {
206 }
209 }
213 }
216 }
220 }
221 thead {
224 }
225 tfoot {
227 }
232 }
235 }
240 }
243 }
247 }
249 div#toctitle {
256 }
261 }
265 }
269 }
273 }
275 /* Workarounds for IE6's broken and incomplete CSS2. */
281 }
287 }
293 }
297 }
302 }
304 /* IE6 sets dynamically generated links as visited. */
306 </style>
308 </head>
309 <body>
311 <h1>
312 git-config(1) Manual Page
313 </h1>
316 <p>git-config -
317 Get and set repository or global options
318 </p>
319 </div>
320 </div>
324 <div class="content"><em>git config</em> [<file-option>] [type] [-z|--null] name [value [value_regex]]
329 <em>git config</em> [<file-option>] [type] [-z|--null] --get-regexp name_regex [value_regex]
338 </div>
342 actually the section and the key separated by a dot, and the value will be
343 escaped.</p></div>
344 <div class="para"><p>Multiple lines can be added to an option by using the <em>--add</em> option.
345 If you want to update or unset an option which can occur on multiple
347 existing values that match the regexp are updated or unset. If
349 prepend a single exclamation mark in front (see also <a href="#EXAMPLES">[EXAMPLES]</a>).</p></div>
350 <div class="para"><p>The type specifier can be either <em>--int</em> or <em>--bool</em>, to make
352 convert the value to the canonical form (simple decimal number for int,
355 checks or transformations are performed on the value.</p></div>
356 <div class="para"><p>The file-option can be one of <em>--system</em>, <em>--global</em> or <em>--file</em>
357 which specify where the values will be read from or written to.
358 The default is to assume the config file of the current repository,
359 .git/config unless defined otherwise with GIT_DIR and GIT_CONFIG
363 <li>
364 <p>
365 The config file is invalid,
366 </p>
367 </li>
368 <li>
369 <p>
370 Can not write to the config file,
371 </p>
372 </li>
373 <li>
374 <p>
375 no section was provided,
376 </p>
377 </li>
378 <li>
379 <p>
380 the section or key is invalid,
381 </p>
382 </li>
383 <li>
384 <p>
385 you try to unset an option which does not exist,
386 </p>
387 </li>
388 <li>
389 <p>
390 you try to unset/set an option for which multiple lines match, or
391 </p>
392 </li>
393 <li>
394 <p>
396 </p>
397 </li>
398 </ol></div>
399 </div>
403 <dt>
404 --replace-all
405 </dt>
406 <dd>
407 <p>
408 Default behavior is to replace at most one line. This replaces
409 all lines matching the key (and optionally the value_regex).
410 </p>
411 </dd>
412 <dt>
413 --add
414 </dt>
415 <dd>
416 <p>
417 Adds a new line to the option without altering any existing
420 </p>
421 </dd>
422 <dt>
423 --get
424 </dt>
425 <dd>
426 <p>
427 Get the value for a given key (optionally filtered by a regex
428 matching the value). Returns error code 1 if the key was not
429 found and error code 2 if multiple key values were found.
430 </p>
431 </dd>
432 <dt>
433 --get-all
434 </dt>
435 <dd>
436 <p>
437 Like get, but does not fail if the number of values for the key
438 is not exactly one.
439 </p>
440 </dd>
441 <dt>
442 --get-regexp
443 </dt>
444 <dd>
445 <p>
446 Like --get-all, but interprets the name as a regular expression.
447 Also outputs the key names.
448 </p>
449 </dd>
450 <dt>
451 --global
452 </dt>
453 <dd>
454 <p>
455 For writing options: write to global ~/.gitconfig file rather than
456 the repository .git/config.
457 </p>
459 from all available files.</p></div>
461 </dd>
462 <dt>
463 --system
464 </dt>
465 <dd>
466 <p>
467 For writing options: write to system-wide $(prefix)/etc/gitconfig
468 rather than the repository .git/config.
469 </p>
471 rather than from all available files.</p></div>
473 </dd>
474 <dt>
475 -f config-file
476 </dt>
477 <dt>
478 --file config-file
479 </dt>
480 <dd>
481 <p>
482 Use the given config file instead of the one specified by GIT_CONFIG.
483 </p>
484 </dd>
485 <dt>
486 --remove-section
487 </dt>
488 <dd>
489 <p>
490 Remove the given section from the configuration file.
491 </p>
492 </dd>
493 <dt>
494 --rename-section
495 </dt>
496 <dd>
497 <p>
498 Rename the given section to a new name.
499 </p>
500 </dd>
501 <dt>
502 --unset
503 </dt>
504 <dd>
505 <p>
506 Remove the line matching the key from config file.
507 </p>
508 </dd>
509 <dt>
510 --unset-all
511 </dt>
512 <dd>
513 <p>
514 Remove all lines matching the key from config file.
515 </p>
516 </dd>
517 <dt>
518 -l
519 </dt>
520 <dt>
521 --list
522 </dt>
523 <dd>
524 <p>
525 List all variables set in config file.
526 </p>
527 </dd>
528 <dt>
529 --bool
530 </dt>
531 <dd>
532 <p>
534 </p>
535 </dd>
536 <dt>
537 --int
538 </dt>
539 <dd>
540 <p>
543 in the config file will cause the value to be multiplied
545 </p>
546 </dd>
547 <dt>
548 --bool-or-int
549 </dt>
550 <dd>
551 <p>
553 either --bool or --int, as described above.
554 </p>
555 </dd>
556 <dt>
557 --path
558 </dt>
559 <dd>
560 <p>
563 specified user. This option has no effect when setting the
565 command line to let your shell do the expansion).
566 </p>
567 </dd>
568 <dt>
569 -z
570 </dt>
571 <dt>
572 --null
573 </dt>
574 <dd>
575 <p>
576 For all options that output values and/or keys, always
577 end values with the null character (instead of a
578 newline). Use newline instead as a delimiter between
579 key and value. This allows for secure parsing of the
580 output without getting confused e.g. by values that
581 contain line breaks.
582 </p>
583 </dd>
584 <dt>
585 --get-colorbool name [stdout-is-tty]
586 </dt>
587 <dd>
588 <p>
591 "false", and is taken into account when configuration says
593 output of the command itself, and exits with status 0 if color
594 is to be used, or exits with status 1 otherwise.
597 </p>
598 </dd>
599 <dt>
600 --get-color name [default]
601 </dt>
602 <dd>
603 <p>
605 output it as the ANSI color escape sequence to the standard
608 </p>
609 </dd>
610 <dt>
611 -e
612 </dt>
613 <dt>
614 --edit
615 </dt>
616 <dd>
617 <p>
618 Opens an editor to modify the specified config file; either
620 </p>
621 </dd>
622 </dl></div>
623 </div>
629 <dt>
630 $GIT_DIR/config
631 </dt>
632 <dd>
633 <p>
634 Repository specific configuration file. (The filename is
635 of course relative to the repository root, not the working
636 directory.)
637 </p>
638 </dd>
639 <dt>
640 ~/.gitconfig
641 </dt>
642 <dd>
643 <p>
644 User-specific configuration file. Also called "global"
645 configuration file.
646 </p>
647 </dd>
648 <dt>
649 $(prefix)/etc/gitconfig
650 </dt>
651 <dd>
652 <p>
653 System-wide configuration file.
654 </p>
655 </dd>
656 </dl></div>
657 <div class="para"><p>If no further options are given, all reading options will read all of these
658 files that are available. If the global or the system-wide configuration
659 file are not available they will be ignored. If the repository configuration
661 error code. However, in neither case will an error message be issued.</p></div>
664 and <em>--unset</em>. <strong><em>git config</em> will only ever change one file at a time</strong>.</p></div>
665 <div class="para"><p>You can override these rules either by command line options or by environment
667 to the global or system-wide file respectively. The GIT_CONFIG environment
668 variable has a similar effect, but you can specify any filename you want.</p></div>
669 </div>
673 <dt>
674 GIT_CONFIG
675 </dt>
676 <dd>
677 <p>
678 Take the configuration from the given file instead of .git/config.
679 Using the "--global" option forces this to ~/.gitconfig. Using the
680 "--system" option forces this to $(prefix)/etc/gitconfig.
681 </p>
682 </dd>
683 </dl></div>
685 </div>
691 <pre><tt>#
692 # This is the config file, and
693 # a '#' or ';' character indicates
694 # a comment
695 #</tt></pre>
696 </div></div>
699 <pre><tt>; core variables
700 [core]
701 ; Don't trust file modes
702 filemode = false</tt></pre>
703 </div></div>
706 <pre><tt>; Our diff algorithm
707 [diff]
708 external = /usr/local/bin/diff-wrapper
709 renames = true</tt></pre>
710 </div></div>
713 <pre><tt>; Proxy settings
714 [core]
716 gitproxy=default-proxy ; for all the rest</tt></pre>
717 </div></div>
722 </div></div>
724 what URL they apply to. Here is how to change the entry for kernel.org
729 </div></div>
730 <div class="para"><p>This makes sure that only the key/value pair for kernel.org is replaced.</p></div>
735 </div></div>
737 you have to provide a regex matching the value of exactly one line.</p></div>
742 </div></div>
747 </div></div>
752 </div></div>
757 </div></div>
758 <div class="para"><p>If you like to live dangerously, you can replace <strong>all</strong> core.gitproxy by a
759 new one with</p></div>
763 </div></div>
764 <div class="para"><p>However, if you really only want to replace the line for the default proxy,
769 </div></div>
770 <div class="para"><p>To actually match only values with an exclamation mark, you have to</p></div>
774 </div></div>
775 <div class="para"><p>To add a new proxy, without altering any of the existing ones, use</p></div>
779 </div></div>
781 script:</p></div>
784 <pre><tt>#!/bin/sh
785 WS=$(git config --get-color color.diff.whitespace "blue reverse")
788 </div></div>
789 </div>
794 is used to store the configuration for that repository, and
797 can be used to store a system-wide default configuration.</p></div>
799 and the porcelains. The variables are divided into sections, wherein
800 the fully qualified variable name of the variable itself is the last
801 dot-separated segment and the section name is everything before the last
802 dot. The variable names are case-insensitive and only alphanumeric
803 characters are allowed. Some variables may appear multiple times.</p></div>
807 blank lines are ignored.</p></div>
809 the name of the section in square brackets and continues until the next
810 section begins. Section names are not case sensitive. Only alphanumeric
812 must belong to some section, which means that there must be a section
813 header before the first setting of a variable.</p></div>
815 put its name in double quotes, separated by space from the section name,
816 in the section header, like in the example below:</p></div>
820 </tt></pre>
821 </div></div>
823 newline (doublequote <tt>"</tt> and backslash have to be escaped as <tt>\"</tt> and <tt>\\</tt>,
824 respectively). Section headers cannot span multiple
825 lines. Variables may belong directly to a section or to a given subsection.
827 don't need to.</p></div>
828 <div class="para"><p>There is also a case insensitive alternative <tt>[section.subsection]</tt> syntax.
829 In this syntax, subsection names follow the same restrictions as for section
830 names.</p></div>
832 header) are recognized as setting variables, in the form
835 The variable names are case-insensitive and only alphanumeric
837 for a given variable; we say then that variable is multivalued.</p></div>
839 Internal whitespace within a variable value is retained verbatim.</p></div>
841 a string, an integer, or a boolean. Boolean values may be given as yes/no,
846 You need to enclose variable values in double quotes if you want to
847 preserve leading or trailing whitespace, or if the variable value contains
851 <div class="para"><p>The following escape sequences (beside <tt>\"</tt> and <tt>\\</tt>) are recognized:
854 char sequences are valid.</p></div>
855 <div class="para"><p>Variable values ending in a <tt>\</tt> are continued on the next line in the
856 customary UNIX fashion.</p></div>
861 <pre><tt># Core variables
862 [core]
863 ; Don't trust file modes
864 filemode = false</tt></pre>
865 </div></div>
868 <pre><tt># Our diff algorithm
869 [diff]
870 external = /usr/local/bin/diff-wrapper
871 renames = true</tt></pre>
872 </div></div>
876 remote = origin
877 merge = refs/heads/devel</tt></pre>
878 </div></div>
881 <pre><tt># Proxy settings
882 [core]
884 gitProxy=default-proxy ; for the rest</tt></pre>
885 </div></div>
888 For command-specific variables, you will find a more detailed description
889 in the appropriate manual page. You will find a description of non-core
890 porcelain configuration variables in the respective porcelain documentation.</p></div>
892 <dt>
893 advice.*
894 </dt>
895 <dd>
896 <p>
899 are:
900 </p>
902 <dt>
903 pushNonFastForward
904 </dt>
905 <dd>
906 <p>
908 non-fast-forward refs. Default: true.
909 </p>
910 </dd>
911 <dt>
912 statusHints
913 </dt>
914 <dd>
915 <p>
916 Directions on how to stage/unstage/add shown in the
918 when writing commit messages. Default: true.
919 </p>
920 </dd>
921 <dt>
922 commitBeforeMerge
923 </dt>
924 <dd>
925 <p>
927 merge to avoid overwritting local changes.
928 Default: true.
929 </p>
930 </dd>
931 <dt>
932 resolveConflict
933 </dt>
934 <dd>
935 <p>
936 Advices shown by various commands when conflicts
937 prevent the operation from being performed.
938 Default: true.
939 </p>
940 </dd>
941 <dt>
942 implicitIdentity
943 </dt>
944 <dd>
945 <p>
946 Advice on how to set your identity configuration when
947 your information is guessed from the system username and
948 domain name. Default: true.
949 </p>
950 </dd>
951 <dt>
952 detachedHead
953 </dt>
954 <dd>
955 <p>
957 move to the detach HEAD state, to instruct how to create
958 a local branch after the fact. Default: true.
959 </p>
960 </dd>
961 </dl></div>
962 </dd>
963 <dt>
964 core.fileMode
965 </dt>
966 <dd>
967 <p>
968 If false, the executable bit differences between the index and
969 the working copy are ignored; useful on broken filesystems like FAT.
971 </p>
972 <div class="para"><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>
973 will probe and set core.fileMode false if appropriate when the
974 repository is created.</p></div>
975 </dd>
976 <dt>
977 core.ignoreCygwinFSTricks
978 </dt>
979 <dd>
980 <p>
981 This option is only used by Cygwin implementation of Git. If false,
982 the Cygwin stat() and lstat() functions are used. This may be useful
983 if your repository consists of a few separate directories joined in
984 one hierarchy using Cygwin mount. If true, Git uses native Win32 API
985 whenever it is possible and falls back to Cygwin functions only to
986 handle symbol links. The native mode is more than twice faster than
987 normal Cygwin l/stat() functions. True by default, unless core.filemode
988 is true, in which case ignoreCygwinFSTricks is ignored as Cygwin's
989 POSIX emulation is required to support core.filemode.
990 </p>
991 </dd>
992 <dt>
993 core.ignorecase
994 </dt>
995 <dd>
996 <p>
997 If true, this option enables various workarounds to enable
998 git to work better on filesystems that are not case sensitive,
999 like FAT. For example, if a directory listing finds
1001 it is really the same file, and continue to remember it as
1002 "Makefile".
1003 </p>
1004 <div class="para"><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>
1005 will probe and set core.ignorecase true if appropriate when the repository
1006 is created.</p></div>
1007 </dd>
1008 <dt>
1009 core.trustctime
1010 </dt>
1011 <dd>
1012 <p>
1013 If false, the ctime differences between the index and the
1014 working copy are ignored; useful when the inode change time
1015 is regularly modified by something outside Git (file system
1016 crawlers and some backup systems).
1018 </p>
1019 </dd>
1020 <dt>
1021 core.quotepath
1022 </dt>
1023 <dd>
1024 <p>
1027 "unusual" characters in the pathname by enclosing the
1028 pathname in a double-quote pair and with backslashes the
1029 same way strings in C source code are quoted. If this
1030 variable is set to false, the bytes higher than 0x80 are
1031 not quoted but output as verbatim. Note that double
1032 quote, backslash and control characters are always
1034 variable.
1035 </p>
1036 </dd>
1037 <dt>
1038 core.eol
1039 </dt>
1040 <dd>
1041 <p>
1042 Sets the line ending type to use in the working directory for
1047 conversion.
1048 </p>
1049 </dd>
1050 <dt>
1051 core.safecrlf
1052 </dt>
1053 <dd>
1054 <p>
1056 end-of-line conversion is active. Git will verify if a command
1057 modifies a file in the work tree either directly or indirectly.
1058 For example, committing a file followed by checking out the
1059 same file should yield the original file in the work tree. If
1060 this is not the case for the current setting of
1062 be set to "warn", in which case git will only warn about an
1063 irreversible conversion but continue the operation.
1064 </p>
1066 When it is enabled, git will convert CRLF to LF during commit and LF to
1067 CRLF during checkout. A file that contains a mixture of LF and
1068 CRLF before the commit cannot be recreated by git. For text
1069 files this is the right thing to do: it corrects line endings
1070 such that we have only LF line endings in the repository.
1071 But for binary files that are accidentally classified as text the
1072 conversion can corrupt data.</p></div>
1074 setting the conversion type explicitly in .gitattributes. Right
1075 after committing you still have the original file in your work
1076 tree and this file is not yet corrupted. You can explicitly tell
1077 git that this file is binary and git will handle the file
1078 appropriately.</p></div>
1080 mixed line endings and the undesired effect of corrupting binary
1081 files cannot be distinguished. In both cases CRLFs are removed
1082 in an irreversible way. For text files this is the right thing
1083 to do because CRLFs are line endings, while for binary files
1084 converting CRLFs corrupts data.</p></div>
1086 file identical to the original file for a different setting of
1094 mechanism.</p></div>
1095 </dd>
1096 <dt>
1097 core.autocrlf
1098 </dt>
1099 <dd>
1100 <p>
1101 Setting this variable to "true" is almost the same as setting
1103 files are not guaranteed to be normalized: files that contain
1106 working directory even though the repository does not have
1108 in which case no output conversion is performed.
1109 </p>
1110 </dd>
1111 <dt>
1112 core.symlinks
1113 </dt>
1114 <dd>
1115 <p>
1116 If false, symbolic links are checked out as small plain files that
1119 file. Useful on filesystems like FAT that do not support
1120 symbolic links.
1121 </p>
1122 <div class="para"><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>
1123 will probe and set core.symlinks false if appropriate when the repository
1124 is created.</p></div>
1125 </dd>
1126 <dt>
1127 core.gitProxy
1128 </dt>
1129 <dd>
1130 <p>
1132 of establishing direct connection to the remote server when
1133 using the git protocol for fetching. If the variable value is
1134 in the "COMMAND for DOMAIN" format, the command is applied only
1135 on hostnames ending with the specified domain string. This variable
1136 may be set multiple times and is matched in the given order;
1137 the first match wins.
1138 </p>
1140 (which always applies universally, without the special "for"
1141 handling).</p></div>
1143 specify that no proxy be used for a given domain pattern.
1144 This is useful for excluding servers inside a firewall from
1145 proxy use, while defaulting to a common proxy for external domains.</p></div>
1146 </dd>
1147 <dt>
1148 core.ignoreStat
1149 </dt>
1150 <dd>
1151 <p>
1152 If true, commands which modify both the working tree and the index
1153 will mark the updated paths with the "assume unchanged" bit in the
1154 index. These marked files are then assumed to stay unchanged in the
1155 working copy, until you mark them otherwise manually - Git will not
1156 detect the file changes by lstat() calls. This is useful on systems
1157 where those are very slow, such as Microsoft Windows.
1159 False by default.
1160 </p>
1161 </dd>
1162 <dt>
1163 core.preferSymlinkRefs
1164 </dt>
1165 <dd>
1166 <p>
1167 Instead of the default "symref" format for HEAD
1168 and other symbolic reference files, use symbolic links.
1169 This is sometimes needed to work with old scripts that
1170 expect HEAD to be a symbolic link.
1171 </p>
1172 </dd>
1173 <dt>
1174 core.bare
1175 </dt>
1176 <dd>
1177 <p>
1179 working directory associated with it. If this is the case a
1180 number of commands that require a working directory will be
1181 disabled, such as <a href="git-add.html">git-add(1)</a> or <a href="git-merge.html">git-merge(1)</a>.
1182 </p>
1183 <div class="para"><p>This setting is automatically guessed by <a href="git-clone.html">git-clone(1)</a> or
1185 repository that ends in "/.git" is assumed to be not bare (bare =
1186 false), while all other repositories are assumed to be bare (bare
1187 = true).</p></div>
1188 </dd>
1189 <dt>
1190 core.worktree
1191 </dt>
1192 <dd>
1193 <p>
1194 Set the path to the root of the work tree.
1195 This can be overridden by the GIT_WORK_TREE environment
1197 an absolute path or a relative path to the .git directory,
1198 either specified by --git-dir or GIT_DIR, or automatically
1199 discovered.
1200 If --git-dir or GIT_DIR are specified but none of
1201 --work-tree, GIT_WORK_TREE and core.worktree is specified,
1202 the current working directory is regarded as the root of the
1203 work tree.
1204 </p>
1206 file in a ".git" subdirectory of a directory, and its value differs
1207 from the latter directory (e.g. "/path/to/.git/config" has
1208 core.worktree set to "/different/path"), which is most likely a
1209 misconfiguration. Running git commands in "/path/to" directory will
1210 still use "/different/path" as the root of the work tree and can cause
1211 great confusion to the users.</p></div>
1212 </dd>
1213 <dt>
1214 core.logAllRefUpdates
1215 </dt>
1216 <dd>
1217 <p>
1219 "$GIT_DIR/logs/<ref>", by appending the new and old
1220 SHA1, the date/time and the reason of the update, but
1221 only when the file exists. If this configuration
1222 variable is set to true, missing "$GIT_DIR/logs/<ref>"
1223 file is automatically created for branch heads.
1224 </p>
1228 a working directory associated with it, and false by
1229 default in a bare repository.</p></div>
1230 </dd>
1231 <dt>
1232 core.repositoryFormatVersion
1233 </dt>
1234 <dd>
1235 <p>
1236 Internal variable identifying the repository format and layout
1237 version.
1238 </p>
1239 </dd>
1240 <dt>
1241 core.sharedRepository
1242 </dt>
1243 <dd>
1244 <p>
1246 several users in a group (making sure all the files and objects are
1248 repository will be readable by all users, additionally to being
1252 user's umask value (whereas the other options will only override
1254 the repo read/write-able for the owner and group, but inaccessible to
1256 repository that is group-readable but not group-writable.
1258 </p>
1259 </dd>
1260 <dt>
1261 core.warnAmbiguousRefs
1262 </dt>
1263 <dd>
1264 <p>
1265 If true, git will warn you if the ref name you passed it is ambiguous
1266 and might match multiple refs in the .git/refs/ tree. True by default.
1267 </p>
1268 </dd>
1269 <dt>
1270 core.compression
1271 </dt>
1272 <dd>
1273 <p>
1277 If set, this provides a default to other compression variables,
1279 </p>
1280 </dd>
1281 <dt>
1282 core.loosecompression
1283 </dt>
1284 <dd>
1285 <p>
1289 slowest. If not set, defaults to core.compression. If that is
1290 not set, defaults to 1 (best speed).
1291 </p>
1292 </dd>
1293 <dt>
1294 core.packedGitWindowSize
1295 </dt>
1296 <dd>
1297 <p>
1298 Number of bytes of a pack file to map into memory in a
1299 single mapping operation. Larger window sizes may allow
1300 your system to process a smaller number of large pack files
1301 more quickly. Smaller window sizes will negatively affect
1302 performance due to increased calls to the operating system's
1303 memory manager, but may improve performance when accessing
1304 a large number of large pack files.
1305 </p>
1308 be reasonable for all users/operating systems. You probably do
1309 not need to adjust this value.</p></div>
1310 <div class="para"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1311 </dd>
1312 <dt>
1313 core.packedGitLimit
1314 </dt>
1315 <dd>
1316 <p>
1317 Maximum number of bytes to map simultaneously into memory
1318 from pack files. If Git needs to access more than this many
1319 bytes at once to complete an operation it will unmap existing
1320 regions to reclaim virtual address space within the process.
1321 </p>
1323 This should be reasonable for all users/operating systems, except on
1324 the largest projects. You probably do not need to adjust this value.</p></div>
1325 <div class="para"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1326 </dd>
1327 <dt>
1328 core.deltaBaseCacheLimit
1329 </dt>
1330 <dd>
1331 <p>
1332 Maximum number of bytes to reserve for caching base objects
1333 that multiple deltafied objects reference. By storing the
1334 entire decompressed base objects in a cache Git is able
1335 to avoid unpacking and decompressing frequently used base
1336 objects multiple times.
1337 </p>
1339 for all users/operating systems, except on the largest projects.
1340 You probably do not need to adjust this value.</p></div>
1341 <div class="para"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1342 </dd>
1343 <dt>
1344 core.bigFileThreshold
1345 </dt>
1346 <dd>
1347 <p>
1348 Files larger than this size are stored deflated, without
1349 attempting delta compression. Storing large files without
1350 delta compression avoids excessive memory usage, at the
1351 slight expense of increased disk usage.
1352 </p>
1354 for most projects as source code and other text files can still
1355 be delta compressed, but larger binary media files won't be.</p></div>
1356 <div class="para"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1357 <div class="para"><p>Currently only <a href="git-fast-import.html">git-fast-import(1)</a> honors this setting.</p></div>
1358 </dd>
1359 <dt>
1360 core.excludesfile
1361 </dt>
1362 <dd>
1363 <p>
1366 of files which are not meant to be tracked. "~/" is expanded
1369 </p>
1370 </dd>
1371 <dt>
1372 core.editor
1373 </dt>
1374 <dd>
1375 <p>
1377 messages by launching an editor uses the value of this
1378 variable when it is set, and the environment variable
1380 </p>
1381 </dd>
1382 <dt>
1383 core.pager
1384 </dt>
1385 <dd>
1386 <p>
1387 The command that git will use to paginate output. Can
1391 pager. One can change these settings by setting the
1393 these settings can be overridden on a project or
1396 environment variable behaviour above, so if you want
1397 to override git's default settings this way, you need
1398 to be explicit. For example, to disable the S option
1401 shell by git, which will translate the final command to
1403 </p>
1404 </dd>
1405 <dt>
1406 core.whitespace
1407 </dt>
1408 <dd>
1409 <p>
1410 A comma separated list of common whitespace problems to
1415 </p>
1417 <li>
1418 <p>
1420 as an error (enabled by default).
1421 </p>
1422 </li>
1423 <li>
1424 <p>
1426 before a tab character in the initial indent part of the line as an
1427 error (enabled by default).
1428 </p>
1429 </li>
1430 <li>
1431 <p>
1433 space characters as an error (not enabled by default).
1434 </p>
1435 </li>
1436 <li>
1437 <p>
1439 the line as an error (not enabled by default).
1440 </p>
1441 </li>
1442 <li>
1443 <p>
1445 (enabled by default).
1446 </p>
1447 </li>
1448 <li>
1449 <p>
1452 </p>
1453 </li>
1454 <li>
1455 <p>
1458 does not trigger if the character before such a carriage-return
1459 is not a whitespace (not enabled by default).
1460 </p>
1461 </li>
1462 </ul></div>
1463 </dd>
1464 <dt>
1465 core.fsyncobjectfiles
1466 </dt>
1467 <dd>
1468 <p>
1470 </p>
1472 data writes properly, but can be useful for filesystems that do not use
1473 journalling (traditional UNIX filesystems) or that only journal metadata
1475 </dd>
1476 <dt>
1477 core.preloadindex
1478 </dt>
1479 <dd>
1480 <p>
1482 </p>
1483 <div class="para"><p>This can speed up operations like <em>git diff</em> and <em>git status</em> especially
1484 on filesystems like NFS that have weak caching semantics and thus
1486 index comparison to the filesystem data in parallel, allowing
1487 overlapping IO's.</p></div>
1488 </dd>
1489 <dt>
1490 core.createObject
1491 </dt>
1492 <dd>
1493 <p>
1495 a delete of the source are used to make sure that object creation
1496 will not overwrite existing objects.
1497 </p>
1500 check that makes sure that existing object files will not get overwritten.</p></div>
1501 </dd>
1502 <dt>
1503 core.notesRef
1504 </dt>
1505 <dd>
1506 <p>
1507 When showing commit messages, also show notes which are stored in
1508 the given ref. The ref must be fully qualified. If the given
1509 ref does not exist, it is not an error but means that no
1510 notes should be printed.
1511 </p>
1512 <div class="para"><p>This setting defaults to "refs/notes/commits", and it can be overridden by
1513 the <em>GIT_NOTES_REF</em> environment variable. See <a href="git-notes.html">git-notes(1)</a>.</p></div>
1514 </dd>
1515 <dt>
1516 core.sparseCheckout
1517 </dt>
1518 <dd>
1519 <p>
1522 </p>
1523 </dd>
1524 <dt>
1525 add.ignore-errors
1526 </dt>
1527 <dd>
1528 <p>
1532 </p>
1533 </dd>
1534 <dt>
1535 alias.*
1536 </dt>
1537 <dd>
1538 <p>
1540 after defining "alias.last = cat-file commit HEAD", the invocation
1542 confusion and troubles with script usage, aliases that
1543 hide existing git commands are ignored. Arguments are split by
1544 spaces, the usual shell quoting and escaping is supported.
1545 quote pair and a backslash can be used to quote them.
1546 </p>
1548 it will be treated as a shell command. For example, defining
1549 "alias.new = !gitk --all --not ORIG_HEAD", the invocation
1550 "git new" is equivalent to running the shell command
1551 "gitk --all --not ORIG_HEAD". Note that shell commands will be
1552 executed from the top-level directory of a repository, which may
1553 not necessarily be the current directory.</p></div>
1554 </dd>
1555 <dt>
1556 am.keepcr
1557 </dt>
1558 <dd>
1559 <p>
1560 If true, git-am will call git-mailsplit for patches in mbox format
1565 </p>
1566 </dd>
1567 <dt>
1568 apply.ignorewhitespace
1569 </dt>
1570 <dd>
1571 <p>
1574 option.
1576 respect all whitespace differences.
1578 </p>
1579 </dd>
1580 <dt>
1581 apply.whitespace
1582 </dt>
1583 <dd>
1584 <p>
1587 </p>
1588 </dd>
1589 <dt>
1590 branch.autosetupmerge
1591 </dt>
1592 <dd>
1593 <p>
1596 starting point branch. Note that even if this option is not set,
1601 done when the starting point is either a local branch or remote
1602 branch. This option defaults to true.
1603 </p>
1604 </dd>
1605 <dt>
1606 branch.autosetuprebase
1607 </dt>
1608 <dd>
1609 <p>
1611 that tracks another branch, this variable tells git to set
1612 up pull to rebase instead of merge (see "branch.<name>.rebase").
1615 other local branches.
1617 remote branches.
1619 branches.
1620 See "branch.autosetupmerge" for details on how to set up a
1621 branch to track another branch.
1622 This option defaults to never.
1623 </p>
1624 </dd>
1625 <dt>
1627 </dt>
1628 <dd>
1629 <p>
1633 </p>
1634 </dd>
1635 <dt>
1637 </dt>
1638 <dd>
1639 <p>
1644 refspec to be marked for merging in FETCH_HEAD. The value is
1645 handled like the remote part of a refspec, and must match a
1646 ref which is fetched from the remote given by
1647 "branch.<name>.remote".
1651 Specify multiple values to get an octopus merge.
1653 another branch in the local repository, you can point
1656 </p>
1657 </dd>
1658 <dt>
1660 </dt>
1661 <dd>
1662 <p>
1665 option values containing whitespace characters are currently not
1666 supported.
1667 </p>
1668 </dd>
1669 <dt>
1671 </dt>
1672 <dd>
1673 <p>
1675 instead of merging the default branch from the default remote when
1676 "git pull" is run.
1679 for details).
1680 </p>
1681 </dd>
1682 <dt>
1684 </dt>
1685 <dd>
1686 <p>
1687 Specify the command to invoke the specified browser. The
1688 specified command is evaluated in shell with the URLs passed
1690 </p>
1691 </dd>
1692 <dt>
1694 </dt>
1695 <dd>
1696 <p>
1697 Override the path for the given tool that may be used to
1700 </p>
1701 </dd>
1702 <dt>
1703 clean.requireForce
1704 </dt>
1705 <dd>
1706 <p>
1707 A boolean to make git-clean do nothing unless given -f
1708 or -n. Defaults to true.
1709 </p>
1710 </dd>
1711 <dt>
1712 color.branch
1713 </dt>
1714 <dd>
1715 <p>
1716 A boolean to enable/disable color in the output of
1718 <tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt> (or <tt>true</tt>), in which case colors are used
1719 only when the output is to a terminal. Defaults to false.
1720 </p>
1721 </dd>
1722 <dt>
1724 </dt>
1725 <dd>
1726 <p>
1730 refs).
1731 </p>
1733 two) and attributes (at most one), separated by spaces. The colors
1734 accepted are <tt>normal</tt>, <tt>black</tt>, <tt>red</tt>, <tt>green</tt>, <tt>yellow</tt>, <tt>blue</tt>,
1735 <tt>magenta</tt>, <tt>cyan</tt> and <tt>white</tt>; the attributes are <tt>bold</tt>, <tt>dim</tt>, <tt>ul</tt>,
1737 second is the background. The position of the attribute, if any,
1738 doesn't matter.</p></div>
1739 </dd>
1740 <dt>
1741 color.diff
1742 </dt>
1743 <dd>
1744 <p>
1747 colors only when the output is to the terminal. Defaults to false.
1748 </p>
1749 </dd>
1750 <dt>
1752 </dt>
1753 <dd>
1754 <p>
1756 which part of the patch to use the specified color, and is one
1760 (highlighting whitespace errors). The values of these variables may be
1762 </p>
1763 </dd>
1764 <dt>
1766 </dt>
1767 <dd>
1768 <p>
1770 of <tt>branch</tt>, <tt>remoteBranch</tt>, <tt>tag</tt>, <tt>stash</tt> or <tt>HEAD</tt> for local
1771 branches, remote tracking branches, tags, stash and HEAD, respectively.
1772 </p>
1773 </dd>
1774 <dt>
1775 color.grep
1776 </dt>
1777 <dd>
1778 <p>
1782 </p>
1783 </dd>
1784 <dt>
1786 </dt>
1787 <dd>
1788 <p>
1790 part of the line to use the specified color, and is one of
1791 </p>
1793 <dt>
1795 </dt>
1796 <dd>
1797 <p>
1799 </p>
1800 </dd>
1801 <dt>
1803 </dt>
1804 <dd>
1805 <p>
1807 </p>
1808 </dd>
1809 <dt>
1811 </dt>
1812 <dd>
1813 <p>
1815 </p>
1816 </dd>
1817 <dt>
1819 </dt>
1820 <dd>
1821 <p>
1823 </p>
1824 </dd>
1825 <dt>
1827 </dt>
1828 <dd>
1829 <p>
1830 matching text
1831 </p>
1832 </dd>
1833 <dt>
1835 </dt>
1836 <dd>
1837 <p>
1838 non-matching text in selected lines
1839 </p>
1840 </dd>
1841 <dt>
1843 </dt>
1844 <dd>
1845 <p>
1848 </p>
1849 </dd>
1850 </dl></div>
1851 <div class="para"><p>The values of these variables may be specified as in color.branch.<slot>.</p></div>
1852 </dd>
1853 <dt>
1854 color.interactive
1855 </dt>
1856 <dd>
1857 <p>
1859 and displays (such as those used by "git-add --interactive").
1861 colors only when the output is to the terminal. Defaults to false.
1862 </p>
1863 </dd>
1864 <dt>
1866 </dt>
1867 <dd>
1868 <p>
1870 output. <tt><slot></tt> may be <tt>prompt</tt>, <tt>header</tt>, <tt>help</tt> or <tt>error</tt>, for
1871 four distinct types of normal output from interactive
1872 commands. The values of these variables may be specified as
1874 </p>
1875 </dd>
1876 <dt>
1877 color.pager
1878 </dt>
1879 <dd>
1880 <p>
1881 A boolean to enable/disable colored output when the pager is in
1882 use (default is true).
1883 </p>
1884 </dd>
1885 <dt>
1886 color.showbranch
1887 </dt>
1888 <dd>
1889 <p>
1890 A boolean to enable/disable color in the output of
1892 <tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt> (or <tt>true</tt>), in which case colors are used
1893 only when the output is to a terminal. Defaults to false.
1894 </p>
1895 </dd>
1896 <dt>
1897 color.status
1898 </dt>
1899 <dd>
1900 <p>
1901 A boolean to enable/disable color in the output of
1903 <tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt> (or <tt>true</tt>), in which case colors are used
1904 only when the output is to a terminal. Defaults to false.
1905 </p>
1906 </dd>
1907 <dt>
1909 </dt>
1910 <dd>
1911 <p>
1918 to red). The values of these variables may be specified as in
1920 </p>
1921 </dd>
1922 <dt>
1923 color.ui
1924 </dt>
1925 <dd>
1926 <p>
1930 terminal. When more specific variables of color.* are set, they always
1931 take precedence over this setting. Defaults to false.
1932 </p>
1933 </dd>
1934 <dt>
1935 commit.status
1936 </dt>
1937 <dd>
1938 <p>
1939 A boolean to enable/disable inclusion of status information in the
1940 commit message template when using an editor to prepare the commit
1941 message. Defaults to true.
1942 </p>
1943 </dd>
1944 <dt>
1945 commit.template
1946 </dt>
1947 <dd>
1948 <p>
1949 Specify a file to use as the template for new commit messages.
1951 specified user's home directory.
1952 </p>
1953 </dd>
1954 <dt>
1955 diff.autorefreshindex
1956 </dt>
1957 <dd>
1958 <p>
1960 files, do not consider stat-only change as changed.
1962 update the cached stat information for paths whose
1963 contents in the work tree match the contents in the
1964 index. This option defaults to true. Note that this
1967 </p>
1968 </dd>
1969 <dt>
1970 diff.external
1971 </dt>
1972 <dd>
1973 <p>
1974 If this config variable is set, diff generation is not
1975 performed using the internal diff machinery, but using the
1976 given command. Can be overridden with the `GIT_EXTERNAL_DIFF'
1977 environment variable. The command is called with parameters
1979 you want to use an external diff program only on a subset of
1981 </p>
1982 </dd>
1983 <dt>
1984 diff.mnemonicprefix
1985 </dt>
1986 <dd>
1987 <p>
1990 this configuration is in effect, reverse diff output also swaps
1991 the order of the prefixes:
1992 </p>
1993 </dd>
1994 <dt>
1995 diff.noprefix
1996 </dt>
1997 <dd>
1998 <p>
2000 </p>
2002 <dt>
2004 </dt>
2005 <dd>
2006 <p>
2007 compares the (i)ndex and the (w)ork tree;
2008 </p>
2009 </dd>
2010 <dt>
2012 </dt>
2013 <dd>
2014 <p>
2015 compares a (c)ommit and the (w)ork tree;
2016 </p>
2017 </dd>
2018 <dt>
2020 </dt>
2021 <dd>
2022 <p>
2023 compares a (c)ommit and the (i)ndex;
2024 </p>
2025 </dd>
2026 <dt>
2028 </dt>
2029 <dd>
2030 <p>
2031 compares an (o)bject and a (w)ork tree entity;
2032 </p>
2033 </dd>
2034 <dt>
2036 </dt>
2037 <dd>
2038 <p>
2040 </p>
2041 </dd>
2042 </dl></div>
2043 </dd>
2044 <dt>
2045 diff.renameLimit
2046 </dt>
2047 <dd>
2048 <p>
2049 The number of files to consider when performing the copy/rename
2051 </p>
2052 </dd>
2053 <dt>
2054 diff.renames
2055 </dt>
2056 <dd>
2057 <p>
2058 Tells git to detect renames. If set to any boolean value, it
2059 will enable basic rename detection. If set to "copies" or
2060 "copy", it will detect copies, as well.
2061 </p>
2062 </dd>
2063 <dt>
2064 diff.suppressBlankEmpty
2065 </dt>
2066 <dd>
2067 <p>
2068 A boolean to inhibit the standard behavior of printing a space
2069 before each empty output line. Defaults to false.
2070 </p>
2071 </dd>
2072 <dt>
2073 diff.tool
2074 </dt>
2075 <dd>
2076 <p>
2080 and plus "kompare".
2081 </p>
2082 </dd>
2083 <dt>
2085 </dt>
2086 <dd>
2087 <p>
2088 Override the path for the given tool. This is useful in case
2089 your tool is not in the PATH.
2090 </p>
2091 </dd>
2092 <dt>
2094 </dt>
2095 <dd>
2096 <p>
2097 Specify the command to invoke the specified diff tool.
2098 The specified command is evaluated in shell with the following
2101 is set to the name of the temporary file containing the contents
2102 of the diff post-image.
2103 </p>
2104 </dd>
2105 <dt>
2106 difftool.prompt
2107 </dt>
2108 <dd>
2109 <p>
2110 Prompt before each invocation of the diff tool.
2111 </p>
2112 </dd>
2113 <dt>
2114 diff.wordRegex
2115 </dt>
2116 <dd>
2117 <p>
2118 A POSIX Extended Regular Expression used to determine what is a "word"
2119 when performing word-by-word difference calculations. Character
2120 sequences that match the regular expression are "words", all other
2122 </p>
2123 </dd>
2124 <dt>
2125 fetch.unpackLimit
2126 </dt>
2127 <dd>
2128 <p>
2129 If the number of objects fetched over the git native
2130 transfer is below this
2131 limit, then the objects will be unpacked into loose object
2132 files. However if the number of received objects equals or
2133 exceeds this limit then the received pack will be stored as
2134 a pack, after adding any missing delta bases. Storing the
2135 pack from a push can make the push operation complete faster,
2136 especially on slow filesystems. If not set, the value of
2138 </p>
2139 </dd>
2140 <dt>
2141 format.attach
2142 </dt>
2143 <dd>
2144 <p>
2145 Enable multipart/mixed attachments as the default for
2147 which will enable attachments as the default and set the
2148 value as the boundary. See the --attach option in
2150 </p>
2151 </dd>
2152 <dt>
2153 format.numbered
2154 </dt>
2155 <dd>
2156 <p>
2157 A boolean which can enable or disable sequence numbers in patch
2158 subjects. It defaults to "auto" which enables it only if there
2159 is more than one patch. It can be enabled or disabled for all
2162 </p>
2163 </dd>
2164 <dt>
2165 format.headers
2166 </dt>
2167 <dd>
2168 <p>
2169 Additional email headers to include in a patch to be submitted
2171 </p>
2172 </dd>
2173 <dt>
2174 format.to
2175 </dt>
2176 <dt>
2177 format.cc
2178 </dt>
2179 <dd>
2180 <p>
2181 Additional recipients to include in a patch to be submitted
2182 by mail. See the --to and --cc options in
2184 </p>
2185 </dd>
2186 <dt>
2187 format.subjectprefix
2188 </dt>
2189 <dd>
2190 <p>
2192 subject prefix. Use this variable to change that prefix.
2193 </p>
2194 </dd>
2195 <dt>
2196 format.signature
2197 </dt>
2198 <dd>
2199 <p>
2200 The default for format-patch is to output a signature containing
2201 the git version number. Use this variable to change that default.
2202 Set this variable to the empty string ("") to suppress
2203 signature generation.
2204 </p>
2205 </dd>
2206 <dt>
2207 format.suffix
2208 </dt>
2209 <dd>
2210 <p>
2211 The default for format-patch is to output files with the suffix
2213 include the dot if you want it).
2214 </p>
2215 </dd>
2216 <dt>
2217 format.pretty
2218 </dt>
2219 <dd>
2220 <p>
2221 The default pretty format for log/show/whatchanged command,
2224 </p>
2225 </dd>
2226 <dt>
2227 format.thread
2228 </dt>
2229 <dd>
2230 <p>
2233 makes every mail a reply to the head of the series,
2234 where the head is chosen from the cover letter, the
2238 value disables threading.
2239 </p>
2240 </dd>
2241 <dt>
2242 format.signoff
2243 </dt>
2244 <dd>
2245 <p>
2248 patch should be a conscious act and means that you certify you have
2249 the rights to submit this work under the same open source license.
2251 </p>
2252 </dd>
2253 <dt>
2254 gc.aggressiveWindow
2255 </dt>
2256 <dd>
2257 <p>
2258 The window size parameter used in the delta compression
2260 to 250.
2261 </p>
2262 </dd>
2263 <dt>
2264 gc.auto
2265 </dt>
2266 <dd>
2267 <p>
2268 When there are approximately more than this many loose
2270 Some Porcelain commands use this command to perform a
2271 light-weight garbage collection from time to time. The
2273 </p>
2274 </dd>
2275 <dt>
2276 gc.autopacklimit
2277 </dt>
2278 <dd>
2279 <p>
2280 When there are more than this many packs that are not
2282 --auto</tt> consolidates them into one larger pack. The
2284 </p>
2285 </dd>
2286 <dt>
2287 gc.packrefs
2288 </dt>
2289 <dd>
2290 <p>
2292 unclonable by Git versions prior to 1.5.1.2 over dumb
2293 transports such as HTTP. This variable determines whether
2295 to enable it within all non-bare repos or it can be set to a
2297 </p>
2298 </dd>
2299 <dt>
2300 gc.pruneexpire
2301 </dt>
2302 <dd>
2303 <p>
2305 Override the grace period with this config variable. The value
2306 "now" may be used to disable this grace period and always prune
2307 unreachable objects immediately.
2308 </p>
2309 </dd>
2310 <dt>
2311 gc.reflogexpire
2312 </dt>
2313 <dt>
2315 </dt>
2316 <dd>
2317 <p>
2320 "refs/stash") in the middle the setting applies only to
2322 </p>
2323 </dd>
2324 <dt>
2325 gc.reflogexpireunreachable
2326 </dt>
2327 <dt>
2329 </dt>
2330 <dd>
2331 <p>
2333 this time and are not reachable from the current tip;
2335 in the middle, the setting applies only to the refs that
2337 </p>
2338 </dd>
2339 <dt>
2340 gc.rerereresolved
2341 </dt>
2342 <dd>
2343 <p>
2344 Records of conflicted merge you resolved earlier are
2347 </p>
2348 </dd>
2349 <dt>
2350 gc.rerereunresolved
2351 </dt>
2352 <dd>
2353 <p>
2354 Records of conflicted merge you have not resolved are
2357 </p>
2358 </dd>
2359 <dt>
2360 gitcvs.commitmsgannotation
2361 </dt>
2362 <dd>
2363 <p>
2364 Append this string to each commit message. Set to empty string
2365 to disable this feature. Defaults to "via git-CVS emulator".
2366 </p>
2367 </dd>
2368 <dt>
2369 gitcvs.enabled
2370 </dt>
2371 <dd>
2372 <p>
2373 Whether the CVS server interface is enabled for this repository.
2375 </p>
2376 </dd>
2377 <dt>
2378 gitcvs.logfile
2379 </dt>
2380 <dd>
2381 <p>
2382 Path to a log file where the CVS server interface well… logs
2384 </p>
2385 </dd>
2386 <dt>
2387 gitcvs.usecrlfattr
2388 </dt>
2389 <dd>
2390 <p>
2391 If true, the server will look up the end-of-line conversion
2393 the attributes force git to treat a file as text,
2395 treat it as text. If they suppress text conversion, the file
2397 the client might otherwise do. If the attributes do not allow
2400 </p>
2401 </dd>
2402 <dt>
2403 gitcvs.allbinary
2404 </dt>
2405 <dd>
2406 <p>
2409 unresolved files are sent to the client in
2411 as binary files, which suppresses any newline munging it
2412 otherwise might do. Alternatively, if it is set to "guess",
2413 then the contents of the file are examined to decide if
2415 </p>
2416 </dd>
2417 <dt>
2418 gitcvs.dbname
2419 </dt>
2420 <dd>
2421 <p>
2422 Database used by git-cvsserver to cache revision information
2423 derived from the git repository. The exact meaning depends on the
2424 used database driver, for SQLite (which is the default driver) this
2425 is a filename. Supports variable substitution (see
2426 <a href="git-cvsserver.html">git-cvsserver(1)</a> for details). May not contain semicolons (<tt>;</tt>).
2428 </p>
2429 </dd>
2430 <dt>
2431 gitcvs.dbdriver
2432 </dt>
2433 <dd>
2434 <p>
2435 Used Perl DBI driver. You can specify any available driver
2436 for this here, but it might not work. git-cvsserver is tested
2441 </p>
2442 </dd>
2443 <dt>
2444 gitcvs.dbuser, gitcvs.dbpass
2445 </dt>
2446 <dd>
2447 <p>
2449 since SQLite has no concept of database users and/or passwords.
2452 </p>
2453 </dd>
2454 <dt>
2455 gitcvs.dbTableNamePrefix
2456 </dt>
2457 <dd>
2458 <p>
2459 Database table name prefix. Prepended to the names of any
2460 database tables used, allowing a single database to be used
2461 for several repositories. Supports variable substitution (see
2463 characters will be replaced with underscores.
2464 </p>
2465 </dd>
2466 </dl></div>
2471 access method.</p></div>
2473 <dt>
2474 gui.commitmsgwidth
2475 </dt>
2476 <dd>
2477 <p>
2478 Defines how wide the commit message window is in the
2480 </p>
2481 </dd>
2482 <dt>
2483 gui.diffcontext
2484 </dt>
2485 <dd>
2486 <p>
2487 Specifies how many context lines should be used in calls to diff
2489 </p>
2490 </dd>
2491 <dt>
2492 gui.encoding
2493 </dt>
2494 <dd>
2495 <p>
2496 Specifies the default encoding to use for displaying of
2500 If this option is not set, the tools default to the
2501 locale encoding.
2502 </p>
2503 </dd>
2504 <dt>
2505 gui.matchtrackingbranch
2506 </dt>
2507 <dd>
2508 <p>
2510 default to tracking remote branches with matching names or
2511 not. Default: "false".
2512 </p>
2513 </dd>
2514 <dt>
2515 gui.newbranchtemplate
2516 </dt>
2517 <dd>
2518 <p>
2519 Is used as suggested name when creating new branches using the
2521 </p>
2522 </dd>
2523 <dt>
2524 gui.pruneduringfetch
2525 </dt>
2526 <dd>
2527 <p>
2529 performing a fetch. The default value is "false".
2530 </p>
2531 </dd>
2532 <dt>
2533 gui.trustmtime
2534 </dt>
2535 <dd>
2536 <p>
2538 timestamp or not. By default the timestamps are not trusted.
2539 </p>
2540 </dd>
2541 <dt>
2542 gui.spellingdictionary
2543 </dt>
2544 <dd>
2545 <p>
2546 Specifies the dictionary used for spell checking commit messages in
2548 off.
2549 </p>
2550 </dd>
2551 <dt>
2552 gui.fastcopyblame
2553 </dt>
2554 <dd>
2555 <p>
2557 location detection. It makes blame significantly faster on huge
2558 repositories at the expense of less thorough copy detection.
2559 </p>
2560 </dd>
2561 <dt>
2562 gui.copyblamethreshold
2563 </dt>
2564 <dd>
2565 <p>
2567 detection, measured in alphanumeric characters. See the
2569 </p>
2570 </dd>
2571 <dt>
2572 gui.blamehistoryctx
2573 </dt>
2574 <dd>
2575 <p>
2576 Specifies the radius of history context in days to show in
2579 variable is set to zero, the whole history is shown.
2580 </p>
2581 </dd>
2582 <dt>
2584 </dt>
2585 <dd>
2586 <p>
2587 Specifies the shell command line to execute when the corresponding item
2589 mandatory for every tool. The command is executed from the root of
2590 the working directory, and in the environment it receives the name of
2594 </p>
2595 </dd>
2596 <dt>
2598 </dt>
2599 <dd>
2600 <p>
2601 Run the tool only if a diff is selected in the GUI. It guarantees
2603 </p>
2604 </dd>
2605 <dt>
2607 </dt>
2608 <dd>
2609 <p>
2610 Run the command silently, without creating a window to display its
2611 output.
2612 </p>
2613 </dd>
2614 <dt>
2616 </dt>
2617 <dd>
2618 <p>
2619 Don't rescan the working directory for changes after the tool
2620 finishes execution.
2621 </p>
2622 </dd>
2623 <dt>
2625 </dt>
2626 <dd>
2627 <p>
2628 Show a confirmation dialog before actually running the tool.
2629 </p>
2630 </dd>
2631 <dt>
2633 </dt>
2634 <dd>
2635 <p>
2636 Request a string argument from the user, and pass it to the tool
2640 the dialog uses a built-in generic prompt; otherwise the exact
2641 value of the variable is used.
2642 </p>
2643 </dd>
2644 <dt>
2646 </dt>
2647 <dd>
2648 <p>
2649 Request a single valid revision from the user, and set the
2652 </p>
2653 </dd>
2654 <dt>
2656 </dt>
2657 <dd>
2658 <p>
2660 This is useful for tools similar to merge or rebase, but not
2661 for things like checkout or reset.
2662 </p>
2663 </dd>
2664 <dt>
2666 </dt>
2667 <dd>
2668 <p>
2669 Specifies the title to use for the prompt dialog. The default
2670 is the tool name.
2671 </p>
2672 </dd>
2673 <dt>
2675 </dt>
2676 <dd>
2677 <p>
2678 Specifies the general prompt string to display at the top of
2680 The default value includes the actual command.
2681 </p>
2682 </dd>
2683 <dt>
2684 help.browser
2685 </dt>
2686 <dd>
2687 <p>
2688 Specify the browser that will be used to display help in the
2690 </p>
2691 </dd>
2692 <dt>
2693 help.format
2694 </dt>
2695 <dd>
2696 <p>
2698 Values <em>man</em>, <em>info</em>, <em>web</em> and <em>html</em> are supported. <em>man</em> is
2700 </p>
2701 </dd>
2702 <dt>
2703 help.autocorrect
2704 </dt>
2705 <dd>
2706 <p>
2707 Automatically correct and execute mistyped commands after
2708 waiting for the given number of deciseconds (0.1 sec). If more
2709 than one command can be deduced from the entered text, nothing
2710 will be executed. If the value of this option is negative,
2711 the corrected command will be executed immediately. If the
2712 value is 0 - the command will be just shown but not executed.
2713 This is the default.
2714 </p>
2715 </dd>
2716 <dt>
2717 http.proxy
2718 </dt>
2719 <dd>
2720 <p>
2724 </p>
2725 </dd>
2726 <dt>
2727 http.sslVerify
2728 </dt>
2729 <dd>
2730 <p>
2731 Whether to verify the SSL certificate when fetching or pushing
2733 variable.
2734 </p>
2735 </dd>
2736 <dt>
2737 http.sslCert
2738 </dt>
2739 <dd>
2740 <p>
2741 File containing the SSL certificate when fetching or pushing
2743 variable.
2744 </p>
2745 </dd>
2746 <dt>
2747 http.sslKey
2748 </dt>
2749 <dd>
2750 <p>
2751 File containing the SSL private key when fetching or pushing
2753 variable.
2754 </p>
2755 </dd>
2756 <dt>
2757 http.sslCertPasswordProtected
2758 </dt>
2759 <dd>
2760 <p>
2761 Enable git's password prompt for the SSL certificate. Otherwise
2762 OpenSSL will prompt the user, possibly many times, if the
2763 certificate or private key is encrypted. Can be overridden by the
2765 </p>
2766 </dd>
2767 <dt>
2768 http.sslCAInfo
2769 </dt>
2770 <dd>
2771 <p>
2772 File containing the certificates to verify the peer with when
2773 fetching or pushing over HTTPS. Can be overridden by the
2775 </p>
2776 </dd>
2777 <dt>
2778 http.sslCAPath
2779 </dt>
2780 <dd>
2781 <p>
2782 Path containing files with the CA certificates to verify the peer
2783 with when fetching or pushing over HTTPS. Can be overridden
2785 </p>
2786 </dd>
2787 <dt>
2788 http.maxRequests
2789 </dt>
2790 <dd>
2791 <p>
2792 How many HTTP requests to launch in parallel. Can be overridden
2794 </p>
2795 </dd>
2796 <dt>
2797 http.minSessions
2798 </dt>
2799 <dd>
2800 <p>
2801 The number of curl sessions (counted across slots) to be kept across
2802 requests. They will not be ended with curl_easy_cleanup() until
2803 http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this
2805 </p>
2806 </dd>
2807 <dt>
2808 http.postBuffer
2809 </dt>
2810 <dd>
2811 <p>
2812 Maximum size in bytes of the buffer used by smart HTTP
2813 transports when POSTing data to the remote system.
2814 For requests larger than this buffer size, HTTP/1.1 and
2815 Transfer-Encoding: chunked is used to avoid creating a
2816 massive pack file locally. Default is 1 MiB, which is
2817 sufficient for most requests.
2818 </p>
2819 </dd>
2820 <dt>
2821 http.lowSpeedLimit, http.lowSpeedTime
2822 </dt>
2823 <dd>
2824 <p>
2829 </p>
2830 </dd>
2831 <dt>
2832 http.noEPSV
2833 </dt>
2834 <dd>
2835 <p>
2836 A boolean which disables using of EPSV ftp command by curl.
2837 This can helpful with some "poor" ftp servers which don't
2839 environment variable. Default is false (curl will use EPSV).
2840 </p>
2841 </dd>
2842 <dt>
2843 i18n.commitEncoding
2844 </dt>
2845 <dd>
2846 <p>
2847 Character encoding the commit messages are stored in; git itself
2848 does not care per se, but this information is necessary e.g. when
2849 importing commits from emails or in the gitk graphical history
2850 browser (and possibly at other places in the future or in other
2851 porcelains). See e.g. <a href="git-mailinfo.html">git-mailinfo(1)</a>. Defaults to <em>utf-8</em>.
2852 </p>
2853 </dd>
2854 <dt>
2855 i18n.logOutputEncoding
2856 </dt>
2857 <dd>
2858 <p>
2859 Character encoding the commit messages are converted to when
2861 </p>
2862 </dd>
2863 <dt>
2864 imap
2865 </dt>
2866 <dd>
2867 <p>
2870 </p>
2871 </dd>
2872 <dt>
2873 init.templatedir
2874 </dt>
2875 <dd>
2876 <p>
2877 Specify the directory from which templates will be copied.
2879 </p>
2880 </dd>
2881 <dt>
2882 instaweb.browser
2883 </dt>
2884 <dd>
2885 <p>
2886 Specify the program that will be used to browse your working
2888 </p>
2889 </dd>
2890 <dt>
2891 instaweb.httpd
2892 </dt>
2893 <dd>
2894 <p>
2895 The HTTP daemon command-line to start gitweb on your working
2897 </p>
2898 </dd>
2899 <dt>
2900 instaweb.local
2901 </dt>
2902 <dd>
2903 <p>
2905 be bound to the local IP (127.0.0.1).
2906 </p>
2907 </dd>
2908 <dt>
2909 instaweb.modulepath
2910 </dt>
2911 <dd>
2912 <p>
2914 </p>
2915 </dd>
2916 <dt>
2917 instaweb.port
2918 </dt>
2919 <dd>
2920 <p>
2921 The port number to bind the gitweb httpd to. See
2923 </p>
2924 </dd>
2925 <dt>
2926 interactive.singlekey
2927 </dt>
2928 <dd>
2929 <p>
2930 In interactive commands, allow the user to provide one-letter
2931 input with a single key (i.e., without hitting enter).
2934 ignored if portable keystroke input is not available.
2935 </p>
2936 </dd>
2937 <dt>
2938 log.date
2939 </dt>
2940 <dd>
2941 <p>
2942 Set default date-time mode for the log command. Setting log.date
2944 following alternatives: {relative,local,default,iso,rfc,short}.
2946 </p>
2947 </dd>
2948 <dt>
2949 log.decorate
2950 </dt>
2951 <dd>
2952 <p>
2953 Print out the ref names of any commits that are shown by the log
2956 specified, the full ref name (including prefix) will be printed.
2958 </p>
2959 </dd>
2960 <dt>
2961 log.showroot
2962 </dt>
2963 <dd>
2964 <p>
2965 If true, the initial commit will be shown as a big creation event.
2966 This is equivalent to a diff against an empty tree.
2967 Tools like <a href="git-log.html">git-log(1)</a> or <a href="git-whatchanged.html">git-whatchanged(1)</a>, which
2968 normally hide the root commit will now show it. True by default.
2969 </p>
2970 </dd>
2971 <dt>
2972 mailmap.file
2973 </dt>
2974 <dd>
2975 <p>
2976 The location of an augmenting mailmap file. The default
2977 mailmap, located in the root of the repository, is loaded
2978 first, then the mailmap file pointed to by this variable.
2979 The location of the mailmap file may be in a repository
2980 subdirectory, or somewhere outside of the repository itself.
2981 See <a href="git-shortlog.html">git-shortlog(1)</a> and <a href="git-blame.html">git-blame(1)</a>.
2982 </p>
2983 </dd>
2984 <dt>
2985 man.viewer
2986 </dt>
2987 <dd>
2988 <p>
2989 Specify the programs that may be used to display help in the
2991 </p>
2992 </dd>
2993 <dt>
2995 </dt>
2996 <dd>
2997 <p>
2998 Specify the command to invoke the specified man viewer. The
2999 specified command is evaluated in shell with the man page
3001 </p>
3002 </dd>
3003 <dt>
3005 </dt>
3006 <dd>
3007 <p>
3008 Override the path for the given tool that may be used to
3010 </p>
3011 </dd>
3012 <dt>
3013 merge.conflictstyle
3014 </dt>
3015 <dd>
3016 <p>
3017 Specify the style in which conflicted hunks are written out to
3018 working tree files upon merge. The default is "merge", which
3021 a <tt>>>>>>>></tt> marker. An alternate style, "diff3", adds a <tt>|||||||</tt>
3023 </p>
3024 </dd>
3025 <dt>
3026 merge.log
3027 </dt>
3028 <dd>
3029 <p>
3030 Whether to include summaries of merged commits in newly created
3031 merge commit messages. False by default.
3032 </p>
3033 </dd>
3034 <dt>
3035 merge.renameLimit
3036 </dt>
3037 <dd>
3038 <p>
3039 The number of files to consider when performing rename detection
3040 during a merge; if not specified, defaults to the value of
3041 diff.renameLimit.
3042 </p>
3043 </dd>
3044 <dt>
3045 merge.stat
3046 </dt>
3047 <dd>
3048 <p>
3049 Whether to print the diffstat between ORIG_HEAD and the merge result
3050 at the end of the merge. True by default.
3051 </p>
3052 </dd>
3053 <dt>
3054 merge.tool
3055 </dt>
3056 <dd>
3057 <p>
3058 Controls which merge resolution program is used by
3062 "opendiff". Any other value is treated is custom merge tool
3064 </p>
3065 </dd>
3066 <dt>
3067 merge.verbosity
3068 </dt>
3069 <dd>
3070 <p>
3071 Controls the amount of output shown by the recursive merge
3072 strategy. Level 0 outputs nothing except a final error
3073 message if conflicts were detected. Level 1 outputs only
3075 above outputs debugging information. The default is level 2.
3077 </p>
3078 </dd>
3079 <dt>
3081 </dt>
3082 <dd>
3083 <p>
3084 Defines a human-readable name for a custom low-level
3086 </p>
3087 </dd>
3088 <dt>
3090 </dt>
3091 <dd>
3092 <p>
3093 Defines the command that implements a custom low-level
3095 </p>
3096 </dd>
3097 <dt>
3099 </dt>
3100 <dd>
3101 <p>
3102 Names a low-level merge driver to be used when
3103 performing an internal merge between common ancestors.
3105 </p>
3106 </dd>
3107 <dt>
3109 </dt>
3110 <dd>
3111 <p>
3112 Override the path for the given tool. This is useful in case
3113 your tool is not in the PATH.
3114 </p>
3115 </dd>
3116 <dt>
3118 </dt>
3119 <dd>
3120 <p>
3121 Specify the command to invoke the specified merge tool. The
3122 specified command is evaluated in shell with the following
3124 containing the common base of the files to be merged, if available;
3127 file containing the contents of the file from the branch being
3129 tool should write the results of a successful merge.
3130 </p>
3131 </dd>
3132 <dt>
3134 </dt>
3135 <dd>
3136 <p>
3137 For a custom merge command, specify whether the exit code of
3138 the merge command can be used to determine whether the merge was
3139 successful. If this is not set to true then the merge target file
3140 timestamp is checked and the merge assumed to have been successful
3141 if the file has been updated, otherwise the user is prompted to
3142 indicate the success of the merge.
3143 </p>
3144 </dd>
3145 <dt>
3146 mergetool.keepBackup
3147 </dt>
3148 <dd>
3149 <p>
3150 After performing a merge, the original file with conflict markers
3154 </p>
3155 </dd>
3156 <dt>
3157 mergetool.keepTemporaries
3158 </dt>
3159 <dd>
3160 <p>
3161 When invoking a custom merge tool, git uses a set of temporary
3162 files to pass to the tool. If the tool returns an error and this
3164 preserved, otherwise they will be removed after the tool has
3166 </p>
3167 </dd>
3168 <dt>
3169 mergetool.prompt
3170 </dt>
3171 <dd>
3172 <p>
3173 Prompt before each invocation of the merge resolution program.
3174 </p>
3175 </dd>
3176 <dt>
3177 notes.displayRef
3178 </dt>
3179 <dd>
3180 <p>
3181 The (fully qualified) refname from which to show notes when
3182 showing commit messages. The value of this variable can be set
3183 to a glob, in which case notes from all matching refs will be
3184 shown. You may also specify this configuration variable
3185 several times. A warning will be issued for refs that do not
3186 exist, but a glob that does not match any refs is silently
3187 ignored.
3188 </p>
3190 environment variable, which must be a colon separated list of refs or
3191 globs.</p></div>
3193 GIT_NOTES_REF) is also implicitly added to the list of refs to be
3194 displayed.</p></div>
3195 </dd>
3196 <dt>
3198 </dt>
3199 <dd>
3200 <p>
3203 automatically copies your notes from the original to the
3205 "notes.rewriteRef" below.
3206 </p>
3207 </dd>
3208 <dt>
3209 notes.rewriteMode
3210 </dt>
3211 <dd>
3212 <p>
3213 When copying notes during a rewrite (see the
3214 "notes.rewrite.<command>" option), determines what to do if
3215 the target commit already has a note. Must be one of
3218 </p>
3220 environment variable.</p></div>
3221 </dd>
3222 <dt>
3223 notes.rewriteRef
3224 </dt>
3225 <dd>
3226 <p>
3227 When copying notes during a rewrite, specifies the (fully
3228 qualified) ref whose notes should be copied. The ref may be a
3229 glob, in which case notes in all matching refs will be copied.
3230 You may also specify this configuration several times.
3231 </p>
3233 enable note rewriting.</p></div>
3235 environment variable, which must be a colon separated list of refs or
3236 globs.</p></div>
3237 </dd>
3238 <dt>
3239 pack.window
3240 </dt>
3241 <dd>
3242 <p>
3244 window size is given on the command line. Defaults to 10.
3245 </p>
3246 </dd>
3247 <dt>
3248 pack.depth
3249 </dt>
3250 <dd>
3251 <p>
3252 The maximum delta depth used by <a href="git-pack-objects.html">git-pack-objects(1)</a> when no
3253 maximum depth is given on the command line. Defaults to 50.
3254 </p>
3255 </dd>
3256 <dt>
3257 pack.windowMemory
3258 </dt>
3259 <dd>
3260 <p>
3262 when no limit is given on the command line. The value can be
3264 limit.
3265 </p>
3266 </dd>
3267 <dt>
3268 pack.compression
3269 </dt>
3270 <dd>
3271 <p>
3275 slowest. If not set, defaults to core.compression. If that is
3277 compromise between speed and compression (currently equivalent
3278 to level 6)."
3279 </p>
3280 </dd>
3281 <dt>
3282 pack.deltaCacheSize
3283 </dt>
3284 <dd>
3285 <p>
3286 The maximum memory in bytes used for caching deltas in
3288 This cache is used to speed up the writing object phase by not
3289 having to recompute the final delta result once the best match
3290 for all objects is found. Repacking large repositories on machines
3291 which are tight with memory might be badly impacted by this though,
3292 especially if this cache pushes the system into swapping.
3294 used to virtually disable this cache. Defaults to 256 MiB.
3295 </p>
3296 </dd>
3297 <dt>
3298 pack.deltaCacheLimit
3299 </dt>
3300 <dd>
3301 <p>
3302 The maximum size of a delta, that is cached in
3304 writing object phase by not having to recompute the final delta
3305 result once the best match for all objects is found. Defaults to 1000.
3306 </p>
3307 </dd>
3308 <dt>
3309 pack.threads
3310 </dt>
3311 <dd>
3312 <p>
3313 Specifies the number of threads to spawn when searching for best
3315 be compiled with pthreads otherwise this option is ignored with a
3316 warning. This is meant to reduce packing time on multiprocessor
3317 machines. The required amount of memory for the delta search window
3318 is however multiplied by the number of threads.
3319 Specifying 0 will cause git to auto-detect the number of CPU's
3320 and set the number of threads accordingly.
3321 </p>
3322 </dd>
3323 <dt>
3324 pack.indexVersion
3325 </dt>
3326 <dd>
3327 <p>
3328 Specify the default pack index version. Valid values are 1 for
3330 the new pack index with capabilities for packs larger than 4 GB
3331 as well as proper protection against the repacking of corrupted
3333 and this config option ignored whenever the corresponding pack is
3334 larger than 2 GB.
3335 </p>
3336 <div class="para"><p>If you have an old git that does not understand the version 2 <tt>*.idx</tt> file,
3338 that will copy both <tt>*.pack</tt> file and corresponding <tt>*.idx</tt> file from the
3339 other side may give you a repository that cannot be accessed with your
3341 you can use <a href="git-index-pack.html">git-index-pack(1)</a> on the *.pack file to regenerate
3343 </dd>
3344 <dt>
3345 pack.packSizeLimit
3346 </dt>
3347 <dd>
3348 <p>
3349 The maximum size of a pack. This setting only affects
3350 packing to a file when repacking, i.e. the git:// protocol
3353 limited to 1 MiB. The default is unlimited.
3355 supported.
3356 </p>
3357 </dd>
3358 <dt>
3360 </dt>
3361 <dd>
3362 <p>
3363 Allows turning on or off pagination of the output of a
3364 particular git subcommand when writing to a tty. If
3366 it takes precedence over this option. To disable pagination for
3368 </p>
3369 </dd>
3370 <dt>
3372 </dt>
3373 <dd>
3374 <p>
3375 Alias for a --pretty= format string, as specified in
3377 as the built-in pretty formats could. For example,
3381 Note that an alias with the same name as a built-in format
3382 will be silently ignored.
3383 </p>
3384 </dd>
3385 <dt>
3386 pull.octopus
3387 </dt>
3388 <dd>
3389 <p>
3390 The default merge strategy to use when pulling multiple branches
3391 at once.
3392 </p>
3393 </dd>
3394 <dt>
3395 pull.twohead
3396 </dt>
3397 <dd>
3398 <p>
3399 The default merge strategy to use when pulling a single branch.
3400 </p>
3401 </dd>
3402 <dt>
3403 push.default
3404 </dt>
3405 <dd>
3406 <p>
3407 Defines the action git push should take if no refspec is given
3408 on the command line, no refspec is configured in the remote, and
3409 no refspec is implied by any of the options given on the command
3410 line. Possible values are:
3411 </p>
3413 <li>
3414 <p>
3416 </p>
3417 </li>
3418 <li>
3419 <p>
3421 All branches having the same name in both ends are considered to be
3422 matching. This is the default.
3423 </p>
3424 </li>
3425 <li>
3426 <p>
3428 </p>
3429 </li>
3430 <li>
3431 <p>
3433 </p>
3434 </li>
3435 </ul></div>
3436 </dd>
3437 <dt>
3438 rebase.stat
3439 </dt>
3440 <dd>
3441 <p>
3442 Whether to show a diffstat of what changed upstream since the last
3443 rebase. False by default.
3444 </p>
3445 </dd>
3446 <dt>
3447 receive.autogc
3448 </dt>
3449 <dd>
3450 <p>
3451 By default, git-receive-pack will run "git-gc --auto" after
3452 receiving data from git-push and updating refs. You can stop
3453 it by setting this variable to false.
3454 </p>
3455 </dd>
3456 <dt>
3457 receive.fsckObjects
3458 </dt>
3459 <dd>
3460 <p>
3461 If it is set to true, git-receive-pack will check all received
3462 objects. It will abort in the case of a malformed object or a
3463 broken link. The result of an abort are only dangling objects.
3464 Defaults to false.
3465 </p>
3466 </dd>
3467 <dt>
3468 receive.unpackLimit
3469 </dt>
3470 <dd>
3471 <p>
3472 If the number of objects received in a push is below this
3473 limit then the objects will be unpacked into loose object
3474 files. However if the number of received objects equals or
3475 exceeds this limit then the received pack will be stored as
3476 a pack, after adding any missing delta bases. Storing the
3477 pack from a push can make the push operation complete faster,
3478 especially on slow filesystems. If not set, the value of
3480 </p>
3481 </dd>
3482 <dt>
3483 receive.denyDeletes
3484 </dt>
3485 <dd>
3486 <p>
3487 If set to true, git-receive-pack will deny a ref update that deletes
3488 the ref. Use this to prevent such a ref deletion via a push.
3489 </p>
3490 </dd>
3491 <dt>
3492 receive.denyCurrentBranch
3493 </dt>
3494 <dd>
3495 <p>
3496 If set to true or "refuse", git-receive-pack will deny a ref update
3497 to the currently checked out branch of a non-bare repository.
3498 Such a push is potentially dangerous because it brings the HEAD
3499 out of sync with the index and working tree. If set to "warn",
3500 print a warning of such a push to stderr, but allow the push to
3501 proceed. If set to false or "ignore", allow such pushes with no
3502 message. Defaults to "refuse".
3503 </p>
3504 </dd>
3505 <dt>
3506 receive.denyNonFastForwards
3507 </dt>
3508 <dd>
3509 <p>
3510 If set to true, git-receive-pack will deny a ref update which is
3511 not a fast-forward. Use this to prevent such an update via a push,
3512 even if that push is forced. This configuration variable is
3513 set when initializing a shared repository.
3514 </p>
3515 </dd>
3516 <dt>
3517 receive.updateserverinfo
3518 </dt>
3519 <dd>
3520 <p>
3521 If set to true, git-receive-pack will run git-update-server-info
3522 after receiving data from git-push and updating refs.
3523 </p>
3524 </dd>
3525 <dt>
3527 </dt>
3528 <dd>
3529 <p>
3532 </p>
3533 </dd>
3534 <dt>
3536 </dt>
3537 <dd>
3538 <p>
3540 </p>
3541 </dd>
3542 <dt>
3544 </dt>
3545 <dd>
3546 <p>
3547 For remotes that require curl (http, https and ftp), the URL to
3548 the proxy to use for that remote. Set to the empty string to
3549 disable proxying for that remote.
3550 </p>
3551 </dd>
3552 <dt>
3554 </dt>
3555 <dd>
3556 <p>
3559 </p>
3560 </dd>
3561 <dt>
3563 </dt>
3564 <dd>
3565 <p>
3568 </p>
3569 </dd>
3570 <dt>
3572 </dt>
3573 <dd>
3574 <p>
3575 If true, pushing to this remote will automatically behave
3577 </p>
3578 </dd>
3579 <dt>
3581 </dt>
3582 <dd>
3583 <p>
3584 If true, this remote will be skipped by default when updating
3587 </p>
3588 </dd>
3589 <dt>
3591 </dt>
3592 <dd>
3593 <p>
3594 If true, this remote will be skipped by default when updating
3597 </p>
3598 </dd>
3599 <dt>
3601 </dt>
3602 <dd>
3603 <p>
3604 The default program to execute on the remote side when pushing. See
3606 </p>
3607 </dd>
3608 <dt>
3610 </dt>
3611 <dd>
3612 <p>
3613 The default program to execute on the remote side when fetching. See
3615 </p>
3616 </dd>
3617 <dt>
3619 </dt>
3620 <dd>
3621 <p>
3622 Setting this value to --no-tags disables automatic tag following when
3625 branch heads.
3626 </p>
3627 </dd>
3628 <dt>
3630 </dt>
3631 <dd>
3632 <p>
3635 </p>
3636 </dd>
3637 <dt>
3639 </dt>
3640 <dd>
3641 <p>
3642 The list of remotes which are fetched by "git remote update
3644 </p>
3645 </dd>
3646 <dt>
3647 repack.usedeltabaseoffset
3648 </dt>
3649 <dd>
3650 <p>
3652 delta-base offset. If you need to share your repository with
3653 git older than version 1.4.4, either directly or via a dumb
3654 protocol such as http, then you need to set this option to
3655 "false" and repack. Access from old git versions over the
3656 native protocol are unaffected by this option.
3657 </p>
3658 </dd>
3659 <dt>
3660 rerere.autoupdate
3661 </dt>
3662 <dd>
3663 <p>
3665 resulting contents after it cleanly resolves conflicts using
3666 previously recorded resolution. Defaults to false.
3667 </p>
3668 </dd>
3669 <dt>
3670 rerere.enabled
3671 </dt>
3672 <dd>
3673 <p>
3674 Activate recording of resolved conflicts, so that identical
3675 conflict hunks can be resolved automatically, should they
3679 </p>
3680 </dd>
3681 <dt>
3682 sendemail.identity
3683 </dt>
3684 <dd>
3685 <p>
3686 A configuration identity. When given, causes values in the
3690 </p>
3691 </dd>
3692 <dt>
3693 sendemail.smtpencryption
3694 </dt>
3695 <dd>
3696 <p>
3699 </p>
3700 </dd>
3701 <dt>
3702 sendemail.smtpssl
3703 </dt>
3704 <dd>
3705 <p>
3707 </p>
3708 </dd>
3709 <dt>
3711 </dt>
3712 <dd>
3713 <p>
3715 found below, taking precedence over those when the this
3716 identity is selected, through command-line or
3718 </p>
3719 </dd>
3720 <dt>
3721 sendemail.aliasesfile
3722 </dt>
3723 <dt>
3724 sendemail.aliasfiletype
3725 </dt>
3726 <dt>
3727 sendemail.bcc
3728 </dt>
3729 <dt>
3730 sendemail.cc
3731 </dt>
3732 <dt>
3733 sendemail.cccmd
3734 </dt>
3735 <dt>
3736 sendemail.chainreplyto
3737 </dt>
3738 <dt>
3739 sendemail.confirm
3740 </dt>
3741 <dt>
3742 sendemail.envelopesender
3743 </dt>
3744 <dt>
3745 sendemail.from
3746 </dt>
3747 <dt>
3748 sendemail.multiedit
3749 </dt>
3750 <dt>
3751 sendemail.signedoffbycc
3752 </dt>
3753 <dt>
3754 sendemail.smtppass
3755 </dt>
3756 <dt>
3757 sendemail.suppresscc
3758 </dt>
3759 <dt>
3760 sendemail.suppressfrom
3761 </dt>
3762 <dt>
3763 sendemail.to
3764 </dt>
3765 <dt>
3766 sendemail.smtpdomain
3767 </dt>
3768 <dt>
3769 sendemail.smtpserver
3770 </dt>
3771 <dt>
3772 sendemail.smtpserverport
3773 </dt>
3774 <dt>
3775 sendemail.smtpuser
3776 </dt>
3777 <dt>
3778 sendemail.thread
3779 </dt>
3780 <dt>
3781 sendemail.validate
3782 </dt>
3783 <dd>
3784 <p>
3786 </p>
3787 </dd>
3788 <dt>
3789 sendemail.signedoffcc
3790 </dt>
3791 <dd>
3792 <p>
3794 </p>
3795 </dd>
3796 <dt>
3797 showbranch.default
3798 </dt>
3799 <dd>
3800 <p>
3803 </p>
3804 </dd>
3805 <dt>
3806 status.relativePaths
3807 </dt>
3808 <dd>
3809 <p>
3812 relative to the repository root (this was the default for git
3813 prior to v1.5.4).
3814 </p>
3815 </dd>
3816 <dt>
3817 status.showUntrackedFiles
3818 </dt>
3819 <dd>
3820 <p>
3821 By default, <a href="git-status.html">git-status(1)</a> and <a href="git-commit.html">git-commit(1)</a> show
3822 files which are not currently tracked by Git. Directories which
3823 contain only untracked files, are shown with the directory name
3824 only. Showing untracked files means that Git needs to lstat() all
3825 all the files in the whole repository, which might be slow on some
3826 systems. So, this variable controls how the commands displays
3827 the untracked files. Possible values are:
3828 </p>
3830 <li>
3831 <p>
3833 </p>
3834 </li>
3835 <li>
3836 <p>
3838 </p>
3839 </li>
3840 <li>
3841 <p>
3843 </p>
3844 </li>
3845 </ul></div>
3847 This variable can be overridden with the -u|--untracked-files option
3848 of <a href="git-status.html">git-status(1)</a> and <a href="git-commit.html">git-commit(1)</a>.</p></div>
3849 </dd>
3850 <dt>
3851 status.submodulesummary
3852 </dt>
3853 <dd>
3854 <p>
3855 Defaults to false.
3856 If this is set to a non zero number or true (identical to -1 or an
3857 unlimited number), the submodule summary will be enabled and a
3858 summary of commits for modified submodules will be shown (see
3860 </p>
3861 </dd>
3862 <dt>
3863 tar.umask
3864 </dt>
3865 <dd>
3866 <p>
3867 This variable can be used to restrict the permission bits of
3868 tar archive entries. The default is 0002, which turns off the
3869 world write bit. The special value "user" indicates that the
3870 archiving user's umask will be used instead. See umask(2) and
3872 </p>
3873 </dd>
3874 <dt>
3875 transfer.unpackLimit
3876 </dt>
3877 <dd>
3878 <p>
3880 not set, the value of this variable is used instead.
3881 The default value is 100.
3882 </p>
3883 </dd>
3884 <dt>
3886 </dt>
3887 <dd>
3888 <p>
3889 Any URL that starts with this value will be rewritten to
3891 large number of repositories, and serves them with multiple
3892 access methods, and some users need to use different access
3893 methods, this feature allows people to specify any of the
3894 equivalent URLs and have git automatically rewrite the URL to
3895 the best alternative for the particular user, even for a
3896 never-before-seen repository on the site. When more than one
3897 insteadOf strings match a given URL, the longest match is used.
3898 </p>
3899 </dd>
3900 <dt>
3902 </dt>
3903 <dd>
3904 <p>
3905 Any URL that starts with this value will not be pushed to;
3907 resulting URL will be pushed to. In cases where some site serves
3908 a large number of repositories, and serves them with multiple
3909 access methods, some of which do not allow push, this feature
3910 allows people to specify a pull-only URL and have git
3911 automatically use an appropriate URL to push, even for a
3912 never-before-seen repository on the site. When more than one
3913 pushInsteadOf strings match a given URL, the longest match is
3914 used. If a remote has an explicit pushurl, git will ignore this
3915 setting for that remote.
3916 </p>
3917 </dd>
3918 <dt>
3919 user.email
3920 </dt>
3921 <dd>
3922 <p>
3923 Your email address to be recorded in any newly created commits.
3925 <em>EMAIL</em> environment variables. See <a href="git-commit-tree.html">git-commit-tree(1)</a>.
3926 </p>
3927 </dd>
3928 <dt>
3929 user.name
3930 </dt>
3931 <dd>
3932 <p>
3933 Your full name to be recorded in any newly created commits.
3936 </p>
3937 </dd>
3938 <dt>
3939 user.signingkey
3940 </dt>
3941 <dd>
3942 <p>
3944 automatically when creating a signed tag, you can override the
3945 default selection with this variable. This option is passed
3946 unchanged to gpg's --local-user parameter, so you may specify a key
3947 using any method that gpg supports.
3948 </p>
3949 </dd>
3950 <dt>
3951 web.browser
3952 </dt>
3953 <dd>
3954 <p>
3955 Specify a web browser that may be used by some commands.
3956 Currently only <a href="git-instaweb.html">git-instaweb(1)</a> and <a href="git-help.html">git-help(1)</a>
3957 may use it.
3958 </p>
3959 </dd>
3960 </dl></div>
3961 </div>
3964 <div class="para"><p>Written by Johannes Schindelin <Johannes.Schindelin@gmx.de></p></div>
3965 </div>
3968 <div class="para"><p>Documentation by Johannes Schindelin, Petr Baudis and the git-list <git@vger.kernel.org>.</p></div>
3969 </div>
3973 </div>
3977 </div>
3978 </div>
3979 </body>
3980 </html>