| blob | 4df5ea86420adf78f26c05ad8b3adb5833a743fe |
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.autocrlf
1039 </dt>
1040 <dd>
1041 <p>
1044 writing to the filesystem. The variable can be set to
1046 reading from the filesystem but files are written out with
1048 "text" (i.e. be subjected to the autocrlf mechanism) based on
1051 </p>
1052 </dd>
1053 <dt>
1054 core.safecrlf
1055 </dt>
1056 <dd>
1057 <p>
1060 modifies a file in the work tree either directly or indirectly.
1061 For example, committing a file followed by checking out the
1062 same file should yield the original file in the work tree. If
1063 this is not the case for the current setting of
1065 be set to "warn", in which case git will only warn about an
1066 irreversible conversion but continue the operation.
1067 </p>
1069 autocrlf=true will convert CRLF to LF during commit and LF to
1070 CRLF during checkout. A file that contains a mixture of LF and
1071 CRLF before the commit cannot be recreated by git. For text
1072 files this is the right thing to do: it corrects line endings
1073 such that we have only LF line endings in the repository.
1074 But for binary files that are accidentally classified as text the
1075 conversion can corrupt data.</p></div>
1077 setting the conversion type explicitly in .gitattributes. Right
1078 after committing you still have the original file in your work
1079 tree and this file is not yet corrupted. You can explicitly tell
1080 git that this file is binary and git will handle the file
1081 appropriately.</p></div>
1083 mixed line endings and the undesired effect of corrupting binary
1084 files cannot be distinguished. In both cases CRLFs are removed
1085 in an irreversible way. For text files this is the right thing
1086 to do because CRLFs are line endings, while for binary files
1087 converting CRLFs corrupts data.</p></div>
1089 file identical to the original file for a different setting of
1097 mechanism.</p></div>
1098 </dd>
1099 <dt>
1100 core.symlinks
1101 </dt>
1102 <dd>
1103 <p>
1104 If false, symbolic links are checked out as small plain files that
1107 file. Useful on filesystems like FAT that do not support
1108 symbolic links.
1109 </p>
1110 <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>
1111 will probe and set core.symlinks false if appropriate when the repository
1112 is created.</p></div>
1113 </dd>
1114 <dt>
1115 core.gitProxy
1116 </dt>
1117 <dd>
1118 <p>
1120 of establishing direct connection to the remote server when
1121 using the git protocol for fetching. If the variable value is
1122 in the "COMMAND for DOMAIN" format, the command is applied only
1123 on hostnames ending with the specified domain string. This variable
1124 may be set multiple times and is matched in the given order;
1125 the first match wins.
1126 </p>
1128 (which always applies universally, without the special "for"
1129 handling).</p></div>
1131 specify that no proxy be used for a given domain pattern.
1132 This is useful for excluding servers inside a firewall from
1133 proxy use, while defaulting to a common proxy for external domains.</p></div>
1134 </dd>
1135 <dt>
1136 core.ignoreStat
1137 </dt>
1138 <dd>
1139 <p>
1140 If true, commands which modify both the working tree and the index
1141 will mark the updated paths with the "assume unchanged" bit in the
1142 index. These marked files are then assumed to stay unchanged in the
1143 working copy, until you mark them otherwise manually - Git will not
1144 detect the file changes by lstat() calls. This is useful on systems
1145 where those are very slow, such as Microsoft Windows.
1147 False by default.
1148 </p>
1149 </dd>
1150 <dt>
1151 core.preferSymlinkRefs
1152 </dt>
1153 <dd>
1154 <p>
1155 Instead of the default "symref" format for HEAD
1156 and other symbolic reference files, use symbolic links.
1157 This is sometimes needed to work with old scripts that
1158 expect HEAD to be a symbolic link.
1159 </p>
1160 </dd>
1161 <dt>
1162 core.bare
1163 </dt>
1164 <dd>
1165 <p>
1167 working directory associated with it. If this is the case a
1168 number of commands that require a working directory will be
1169 disabled, such as <a href="git-add.html">git-add(1)</a> or <a href="git-merge.html">git-merge(1)</a>.
1170 </p>
1171 <div class="para"><p>This setting is automatically guessed by <a href="git-clone.html">git-clone(1)</a> or
1173 repository that ends in "/.git" is assumed to be not bare (bare =
1174 false), while all other repositories are assumed to be bare (bare
1175 = true).</p></div>
1176 </dd>
1177 <dt>
1178 core.worktree
1179 </dt>
1180 <dd>
1181 <p>
1182 Set the path to the root of the work tree.
1183 This can be overridden by the GIT_WORK_TREE environment
1185 an absolute path or a relative path to the .git directory,
1186 either specified by --git-dir or GIT_DIR, or automatically
1187 discovered.
1188 If --git-dir or GIT_DIR are specified but none of
1189 --work-tree, GIT_WORK_TREE and core.worktree is specified,
1190 the current working directory is regarded as the root of the
1191 work tree.
1192 </p>
1194 file in a ".git" subdirectory of a directory, and its value differs
1195 from the latter directory (e.g. "/path/to/.git/config" has
1196 core.worktree set to "/different/path"), which is most likely a
1197 misconfiguration. Running git commands in "/path/to" directory will
1198 still use "/different/path" as the root of the work tree and can cause
1199 great confusion to the users.</p></div>
1200 </dd>
1201 <dt>
1202 core.logAllRefUpdates
1203 </dt>
1204 <dd>
1205 <p>
1207 "$GIT_DIR/logs/<ref>", by appending the new and old
1208 SHA1, the date/time and the reason of the update, but
1209 only when the file exists. If this configuration
1210 variable is set to true, missing "$GIT_DIR/logs/<ref>"
1211 file is automatically created for branch heads.
1212 </p>
1216 a working directory associated with it, and false by
1217 default in a bare repository.</p></div>
1218 </dd>
1219 <dt>
1220 core.repositoryFormatVersion
1221 </dt>
1222 <dd>
1223 <p>
1224 Internal variable identifying the repository format and layout
1225 version.
1226 </p>
1227 </dd>
1228 <dt>
1229 core.sharedRepository
1230 </dt>
1231 <dd>
1232 <p>
1234 several users in a group (making sure all the files and objects are
1236 repository will be readable by all users, additionally to being
1240 user's umask value (whereas the other options will only override
1242 the repo read/write-able for the owner and group, but inaccessible to
1244 repository that is group-readable but not group-writable.
1246 </p>
1247 </dd>
1248 <dt>
1249 core.warnAmbiguousRefs
1250 </dt>
1251 <dd>
1252 <p>
1253 If true, git will warn you if the ref name you passed it is ambiguous
1254 and might match multiple refs in the .git/refs/ tree. True by default.
1255 </p>
1256 </dd>
1257 <dt>
1258 core.compression
1259 </dt>
1260 <dd>
1261 <p>
1265 If set, this provides a default to other compression variables,
1267 </p>
1268 </dd>
1269 <dt>
1270 core.loosecompression
1271 </dt>
1272 <dd>
1273 <p>
1277 slowest. If not set, defaults to core.compression. If that is
1278 not set, defaults to 1 (best speed).
1279 </p>
1280 </dd>
1281 <dt>
1282 core.packedGitWindowSize
1283 </dt>
1284 <dd>
1285 <p>
1286 Number of bytes of a pack file to map into memory in a
1287 single mapping operation. Larger window sizes may allow
1288 your system to process a smaller number of large pack files
1289 more quickly. Smaller window sizes will negatively affect
1290 performance due to increased calls to the operating system's
1291 memory manager, but may improve performance when accessing
1292 a large number of large pack files.
1293 </p>
1296 be reasonable for all users/operating systems. You probably do
1297 not need to adjust this value.</p></div>
1298 <div class="para"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1299 </dd>
1300 <dt>
1301 core.packedGitLimit
1302 </dt>
1303 <dd>
1304 <p>
1305 Maximum number of bytes to map simultaneously into memory
1306 from pack files. If Git needs to access more than this many
1307 bytes at once to complete an operation it will unmap existing
1308 regions to reclaim virtual address space within the process.
1309 </p>
1311 This should be reasonable for all users/operating systems, except on
1312 the largest projects. You probably do not need to adjust this value.</p></div>
1313 <div class="para"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1314 </dd>
1315 <dt>
1316 core.deltaBaseCacheLimit
1317 </dt>
1318 <dd>
1319 <p>
1320 Maximum number of bytes to reserve for caching base objects
1321 that multiple deltafied objects reference. By storing the
1322 entire decompressed base objects in a cache Git is able
1323 to avoid unpacking and decompressing frequently used base
1324 objects multiple times.
1325 </p>
1327 for all users/operating systems, except on the largest projects.
1328 You probably do not need to adjust this value.</p></div>
1329 <div class="para"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1330 </dd>
1331 <dt>
1332 core.bigFileThreshold
1333 </dt>
1334 <dd>
1335 <p>
1336 Files larger than this size are stored deflated, without
1337 attempting delta compression. Storing large files without
1338 delta compression avoids excessive memory usage, at the
1339 slight expense of increased disk usage.
1340 </p>
1342 for most projects as source code and other text files can still
1343 be delta compressed, but larger binary media files won't be.</p></div>
1344 <div class="para"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1345 <div class="para"><p>Currently only <a href="git-fast-import.html">git-fast-import(1)</a> honors this setting.</p></div>
1346 </dd>
1347 <dt>
1348 core.excludesfile
1349 </dt>
1350 <dd>
1351 <p>
1354 of files which are not meant to be tracked. "~/" is expanded
1357 </p>
1358 </dd>
1359 <dt>
1360 core.editor
1361 </dt>
1362 <dd>
1363 <p>
1365 messages by launching an editor uses the value of this
1366 variable when it is set, and the environment variable
1368 </p>
1369 </dd>
1370 <dt>
1371 core.pager
1372 </dt>
1373 <dd>
1374 <p>
1375 The command that git will use to paginate output. Can
1379 pager. One can change these settings by setting the
1381 these settings can be overridden on a project or
1384 environment variable behaviour above, so if you want
1385 to override git's default settings this way, you need
1386 to be explicit. For example, to disable the S option
1389 shell by git, which will translate the final command to
1391 </p>
1392 </dd>
1393 <dt>
1394 core.whitespace
1395 </dt>
1396 <dd>
1397 <p>
1398 A comma separated list of common whitespace problems to
1403 </p>
1405 <li>
1406 <p>
1408 as an error (enabled by default).
1409 </p>
1410 </li>
1411 <li>
1412 <p>
1414 before a tab character in the initial indent part of the line as an
1415 error (enabled by default).
1416 </p>
1417 </li>
1418 <li>
1419 <p>
1421 space characters as an error (not enabled by default).
1422 </p>
1423 </li>
1424 <li>
1425 <p>
1427 (enabled by default).
1428 </p>
1429 </li>
1430 <li>
1431 <p>
1434 </p>
1435 </li>
1436 <li>
1437 <p>
1440 does not trigger if the character before such a carriage-return
1441 is not a whitespace (not enabled by default).
1442 </p>
1443 </li>
1444 </ul></div>
1445 </dd>
1446 <dt>
1447 core.fsyncobjectfiles
1448 </dt>
1449 <dd>
1450 <p>
1452 </p>
1454 data writes properly, but can be useful for filesystems that do not use
1455 journalling (traditional UNIX filesystems) or that only journal metadata
1457 </dd>
1458 <dt>
1459 core.preloadindex
1460 </dt>
1461 <dd>
1462 <p>
1464 </p>
1465 <div class="para"><p>This can speed up operations like <em>git diff</em> and <em>git status</em> especially
1466 on filesystems like NFS that have weak caching semantics and thus
1468 index comparison to the filesystem data in parallel, allowing
1469 overlapping IO's.</p></div>
1470 </dd>
1471 <dt>
1472 core.createObject
1473 </dt>
1474 <dd>
1475 <p>
1477 a delete of the source are used to make sure that object creation
1478 will not overwrite existing objects.
1479 </p>
1482 check that makes sure that existing object files will not get overwritten.</p></div>
1483 </dd>
1484 <dt>
1485 core.notesRef
1486 </dt>
1487 <dd>
1488 <p>
1489 When showing commit messages, also show notes which are stored in
1490 the given ref. This ref is expected to contain files named
1491 after the full SHA-1 of the commit they annotate. The ref
1492 must be fully qualified.
1493 </p>
1495 appended to the commit message, separated by a "Notes (<refname>):"
1497 given ref itself does not exist, it is not an error, but means that no
1498 notes should be printed.</p></div>
1501 </dd>
1502 <dt>
1503 core.sparseCheckout
1504 </dt>
1505 <dd>
1506 <p>
1509 </p>
1510 </dd>
1511 <dt>
1512 add.ignore-errors
1513 </dt>
1514 <dd>
1515 <p>
1519 </p>
1520 </dd>
1521 <dt>
1522 alias.*
1523 </dt>
1524 <dd>
1525 <p>
1527 after defining "alias.last = cat-file commit HEAD", the invocation
1529 confusion and troubles with script usage, aliases that
1530 hide existing git commands are ignored. Arguments are split by
1531 spaces, the usual shell quoting and escaping is supported.
1532 quote pair and a backslash can be used to quote them.
1533 </p>
1535 it will be treated as a shell command. For example, defining
1536 "alias.new = !gitk --all --not ORIG_HEAD", the invocation
1537 "git new" is equivalent to running the shell command
1538 "gitk --all --not ORIG_HEAD". Note that shell commands will be
1539 executed from the top-level directory of a repository, which may
1540 not necessarily be the current directory.</p></div>
1541 </dd>
1542 <dt>
1543 am.keepcr
1544 </dt>
1545 <dd>
1546 <p>
1547 If true, git-am will call git-mailsplit for patches in mbox format
1552 </p>
1553 </dd>
1554 <dt>
1555 apply.ignorewhitespace
1556 </dt>
1557 <dd>
1558 <p>
1561 option.
1563 respect all whitespace differences.
1565 </p>
1566 </dd>
1567 <dt>
1568 apply.whitespace
1569 </dt>
1570 <dd>
1571 <p>
1574 </p>
1575 </dd>
1576 <dt>
1577 branch.autosetupmerge
1578 </dt>
1579 <dd>
1580 <p>
1583 starting point branch. Note that even if this option is not set,
1588 done when the starting point is either a local branch or remote
1589 branch. This option defaults to true.
1590 </p>
1591 </dd>
1592 <dt>
1593 branch.autosetuprebase
1594 </dt>
1595 <dd>
1596 <p>
1598 that tracks another branch, this variable tells git to set
1599 up pull to rebase instead of merge (see "branch.<name>.rebase").
1602 other local branches.
1604 remote branches.
1606 branches.
1607 See "branch.autosetupmerge" for details on how to set up a
1608 branch to track another branch.
1609 This option defaults to never.
1610 </p>
1611 </dd>
1612 <dt>
1614 </dt>
1615 <dd>
1616 <p>
1620 </p>
1621 </dd>
1622 <dt>
1624 </dt>
1625 <dd>
1626 <p>
1631 refspec to be marked for merging in FETCH_HEAD. The value is
1632 handled like the remote part of a refspec, and must match a
1633 ref which is fetched from the remote given by
1634 "branch.<name>.remote".
1638 Specify multiple values to get an octopus merge.
1640 another branch in the local repository, you can point
1643 </p>
1644 </dd>
1645 <dt>
1647 </dt>
1648 <dd>
1649 <p>
1652 option values containing whitespace characters are currently not
1653 supported.
1654 </p>
1655 </dd>
1656 <dt>
1658 </dt>
1659 <dd>
1660 <p>
1662 instead of merging the default branch from the default remote when
1663 "git pull" is run.
1666 for details).
1667 </p>
1668 </dd>
1669 <dt>
1671 </dt>
1672 <dd>
1673 <p>
1674 Specify the command to invoke the specified browser. The
1675 specified command is evaluated in shell with the URLs passed
1677 </p>
1678 </dd>
1679 <dt>
1681 </dt>
1682 <dd>
1683 <p>
1684 Override the path for the given tool that may be used to
1687 </p>
1688 </dd>
1689 <dt>
1690 clean.requireForce
1691 </dt>
1692 <dd>
1693 <p>
1694 A boolean to make git-clean do nothing unless given -f
1695 or -n. Defaults to true.
1696 </p>
1697 </dd>
1698 <dt>
1699 color.branch
1700 </dt>
1701 <dd>
1702 <p>
1703 A boolean to enable/disable color in the output of
1705 <tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt> (or <tt>true</tt>), in which case colors are used
1706 only when the output is to a terminal. Defaults to false.
1707 </p>
1708 </dd>
1709 <dt>
1711 </dt>
1712 <dd>
1713 <p>
1717 refs).
1718 </p>
1720 two) and attributes (at most one), separated by spaces. The colors
1721 accepted are <tt>normal</tt>, <tt>black</tt>, <tt>red</tt>, <tt>green</tt>, <tt>yellow</tt>, <tt>blue</tt>,
1722 <tt>magenta</tt>, <tt>cyan</tt> and <tt>white</tt>; the attributes are <tt>bold</tt>, <tt>dim</tt>, <tt>ul</tt>,
1724 second is the background. The position of the attribute, if any,
1725 doesn't matter.</p></div>
1726 </dd>
1727 <dt>
1728 color.diff
1729 </dt>
1730 <dd>
1731 <p>
1734 colors only when the output is to the terminal. Defaults to false.
1735 </p>
1736 </dd>
1737 <dt>
1739 </dt>
1740 <dd>
1741 <p>
1743 which part of the patch to use the specified color, and is one
1747 (highlighting whitespace errors). The values of these variables may be
1749 </p>
1750 </dd>
1751 <dt>
1752 color.grep
1753 </dt>
1754 <dd>
1755 <p>
1759 </p>
1760 </dd>
1761 <dt>
1763 </dt>
1764 <dd>
1765 <p>
1767 part of the line to use the specified color, and is one of
1768 </p>
1770 <dt>
1772 </dt>
1773 <dd>
1774 <p>
1776 </p>
1777 </dd>
1778 <dt>
1780 </dt>
1781 <dd>
1782 <p>
1784 </p>
1785 </dd>
1786 <dt>
1788 </dt>
1789 <dd>
1790 <p>
1792 </p>
1793 </dd>
1794 <dt>
1796 </dt>
1797 <dd>
1798 <p>
1800 </p>
1801 </dd>
1802 <dt>
1804 </dt>
1805 <dd>
1806 <p>
1807 matching text
1808 </p>
1809 </dd>
1810 <dt>
1812 </dt>
1813 <dd>
1814 <p>
1815 non-matching text in selected lines
1816 </p>
1817 </dd>
1818 <dt>
1820 </dt>
1821 <dd>
1822 <p>
1825 </p>
1826 </dd>
1827 </dl></div>
1828 <div class="para"><p>The values of these variables may be specified as in color.branch.<slot>.</p></div>
1829 </dd>
1830 <dt>
1831 color.interactive
1832 </dt>
1833 <dd>
1834 <p>
1836 and displays (such as those used by "git-add --interactive").
1838 colors only when the output is to the terminal. Defaults to false.
1839 </p>
1840 </dd>
1841 <dt>
1843 </dt>
1844 <dd>
1845 <p>
1847 output. <tt><slot></tt> may be <tt>prompt</tt>, <tt>header</tt>, <tt>help</tt> or <tt>error</tt>, for
1848 four distinct types of normal output from interactive
1849 commands. The values of these variables may be specified as
1851 </p>
1852 </dd>
1853 <dt>
1854 color.pager
1855 </dt>
1856 <dd>
1857 <p>
1858 A boolean to enable/disable colored output when the pager is in
1859 use (default is true).
1860 </p>
1861 </dd>
1862 <dt>
1863 color.showbranch
1864 </dt>
1865 <dd>
1866 <p>
1867 A boolean to enable/disable color in the output of
1869 <tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt> (or <tt>true</tt>), in which case colors are used
1870 only when the output is to a terminal. Defaults to false.
1871 </p>
1872 </dd>
1873 <dt>
1874 color.status
1875 </dt>
1876 <dd>
1877 <p>
1878 A boolean to enable/disable color in the output of
1880 <tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt> (or <tt>true</tt>), in which case colors are used
1881 only when the output is to a terminal. Defaults to false.
1882 </p>
1883 </dd>
1884 <dt>
1886 </dt>
1887 <dd>
1888 <p>
1895 to red). The values of these variables may be specified as in
1897 </p>
1898 </dd>
1899 <dt>
1900 color.ui
1901 </dt>
1902 <dd>
1903 <p>
1907 terminal. When more specific variables of color.* are set, they always
1908 take precedence over this setting. Defaults to false.
1909 </p>
1910 </dd>
1911 <dt>
1912 commit.status
1913 </dt>
1914 <dd>
1915 <p>
1916 A boolean to enable/disable inclusion of status information in the
1917 commit message template when using an editor to prepare the commit
1918 message. Defaults to true.
1919 </p>
1920 </dd>
1921 <dt>
1922 commit.template
1923 </dt>
1924 <dd>
1925 <p>
1926 Specify a file to use as the template for new commit messages.
1928 specified user's home directory.
1929 </p>
1930 </dd>
1931 <dt>
1932 diff.autorefreshindex
1933 </dt>
1934 <dd>
1935 <p>
1937 files, do not consider stat-only change as changed.
1939 update the cached stat information for paths whose
1940 contents in the work tree match the contents in the
1941 index. This option defaults to true. Note that this
1944 </p>
1945 </dd>
1946 <dt>
1947 diff.external
1948 </dt>
1949 <dd>
1950 <p>
1951 If this config variable is set, diff generation is not
1952 performed using the internal diff machinery, but using the
1953 given command. Can be overridden with the `GIT_EXTERNAL_DIFF'
1954 environment variable. The command is called with parameters
1956 you want to use an external diff program only on a subset of
1958 </p>
1959 </dd>
1960 <dt>
1961 diff.mnemonicprefix
1962 </dt>
1963 <dd>
1964 <p>
1967 this configuration is in effect, reverse diff output also swaps
1968 the order of the prefixes:
1969 </p>
1971 <dt>
1973 </dt>
1974 <dd>
1975 <p>
1976 compares the (i)ndex and the (w)ork tree;
1977 </p>
1978 </dd>
1979 <dt>
1981 </dt>
1982 <dd>
1983 <p>
1984 compares a (c)ommit and the (w)ork tree;
1985 </p>
1986 </dd>
1987 <dt>
1989 </dt>
1990 <dd>
1991 <p>
1992 compares a (c)ommit and the (i)ndex;
1993 </p>
1994 </dd>
1995 <dt>
1997 </dt>
1998 <dd>
1999 <p>
2000 compares an (o)bject and a (w)ork tree entity;
2001 </p>
2002 </dd>
2003 <dt>
2005 </dt>
2006 <dd>
2007 <p>
2009 </p>
2010 </dd>
2011 </dl></div>
2012 </dd>
2013 <dt>
2014 diff.renameLimit
2015 </dt>
2016 <dd>
2017 <p>
2018 The number of files to consider when performing the copy/rename
2020 </p>
2021 </dd>
2022 <dt>
2023 diff.renames
2024 </dt>
2025 <dd>
2026 <p>
2027 Tells git to detect renames. If set to any boolean value, it
2028 will enable basic rename detection. If set to "copies" or
2029 "copy", it will detect copies, as well.
2030 </p>
2031 </dd>
2032 <dt>
2033 diff.suppressBlankEmpty
2034 </dt>
2035 <dd>
2036 <p>
2037 A boolean to inhibit the standard behavior of printing a space
2038 before each empty output line. Defaults to false.
2039 </p>
2040 </dd>
2041 <dt>
2042 diff.tool
2043 </dt>
2044 <dd>
2045 <p>
2049 and plus "kompare".
2050 </p>
2051 </dd>
2052 <dt>
2054 </dt>
2055 <dd>
2056 <p>
2057 Override the path for the given tool. This is useful in case
2058 your tool is not in the PATH.
2059 </p>
2060 </dd>
2061 <dt>
2063 </dt>
2064 <dd>
2065 <p>
2066 Specify the command to invoke the specified diff tool.
2067 The specified command is evaluated in shell with the following
2070 is set to the name of the temporary file containing the contents
2071 of the diff post-image.
2072 </p>
2073 </dd>
2074 <dt>
2075 difftool.prompt
2076 </dt>
2077 <dd>
2078 <p>
2079 Prompt before each invocation of the diff tool.
2080 </p>
2081 </dd>
2082 <dt>
2083 diff.wordRegex
2084 </dt>
2085 <dd>
2086 <p>
2087 A POSIX Extended Regular Expression used to determine what is a "word"
2088 when performing word-by-word difference calculations. Character
2089 sequences that match the regular expression are "words", all other
2091 </p>
2092 </dd>
2093 <dt>
2094 fetch.unpackLimit
2095 </dt>
2096 <dd>
2097 <p>
2098 If the number of objects fetched over the git native
2099 transfer is below this
2100 limit, then the objects will be unpacked into loose object
2101 files. However if the number of received objects equals or
2102 exceeds this limit then the received pack will be stored as
2103 a pack, after adding any missing delta bases. Storing the
2104 pack from a push can make the push operation complete faster,
2105 especially on slow filesystems. If not set, the value of
2107 </p>
2108 </dd>
2109 <dt>
2110 format.attach
2111 </dt>
2112 <dd>
2113 <p>
2114 Enable multipart/mixed attachments as the default for
2116 which will enable attachments as the default and set the
2117 value as the boundary. See the --attach option in
2119 </p>
2120 </dd>
2121 <dt>
2122 format.numbered
2123 </dt>
2124 <dd>
2125 <p>
2126 A boolean which can enable or disable sequence numbers in patch
2127 subjects. It defaults to "auto" which enables it only if there
2128 is more than one patch. It can be enabled or disabled for all
2131 </p>
2132 </dd>
2133 <dt>
2134 format.headers
2135 </dt>
2136 <dd>
2137 <p>
2138 Additional email headers to include in a patch to be submitted
2140 </p>
2141 </dd>
2142 <dt>
2143 format.cc
2144 </dt>
2145 <dd>
2146 <p>
2147 Additional "Cc:" headers to include in a patch to be submitted
2149 </p>
2150 </dd>
2151 <dt>
2152 format.subjectprefix
2153 </dt>
2154 <dd>
2155 <p>
2157 subject prefix. Use this variable to change that prefix.
2158 </p>
2159 </dd>
2160 <dt>
2161 format.suffix
2162 </dt>
2163 <dd>
2164 <p>
2165 The default for format-patch is to output files with the suffix
2167 include the dot if you want it).
2168 </p>
2169 </dd>
2170 <dt>
2171 format.pretty
2172 </dt>
2173 <dd>
2174 <p>
2175 The default pretty format for log/show/whatchanged command,
2178 </p>
2179 </dd>
2180 <dt>
2181 format.thread
2182 </dt>
2183 <dd>
2184 <p>
2187 makes every mail a reply to the head of the series,
2188 where the head is chosen from the cover letter, the
2192 value disables threading.
2193 </p>
2194 </dd>
2195 <dt>
2196 format.signoff
2197 </dt>
2198 <dd>
2199 <p>
2202 patch should be a conscious act and means that you certify you have
2203 the rights to submit this work under the same open source license.
2205 </p>
2206 </dd>
2207 <dt>
2208 gc.aggressiveWindow
2209 </dt>
2210 <dd>
2211 <p>
2212 The window size parameter used in the delta compression
2214 to 10.
2215 </p>
2216 </dd>
2217 <dt>
2218 gc.auto
2219 </dt>
2220 <dd>
2221 <p>
2222 When there are approximately more than this many loose
2224 Some Porcelain commands use this command to perform a
2225 light-weight garbage collection from time to time. The
2227 </p>
2228 </dd>
2229 <dt>
2230 gc.autopacklimit
2231 </dt>
2232 <dd>
2233 <p>
2234 When there are more than this many packs that are not
2236 --auto</tt> consolidates them into one larger pack. The
2238 </p>
2239 </dd>
2240 <dt>
2241 gc.packrefs
2242 </dt>
2243 <dd>
2244 <p>
2246 unclonable by Git versions prior to 1.5.1.2 over dumb
2247 transports such as HTTP. This variable determines whether
2249 to enable it within all non-bare repos or it can be set to a
2251 </p>
2252 </dd>
2253 <dt>
2254 gc.pruneexpire
2255 </dt>
2256 <dd>
2257 <p>
2259 Override the grace period with this config variable. The value
2260 "now" may be used to disable this grace period and always prune
2261 unreachable objects immediately.
2262 </p>
2263 </dd>
2264 <dt>
2265 gc.reflogexpire
2266 </dt>
2267 <dd>
2268 <p>
2270 this time; defaults to 90 days.
2271 </p>
2272 </dd>
2273 <dt>
2274 gc.reflogexpireunreachable
2275 </dt>
2276 <dd>
2277 <p>
2279 this time and are not reachable from the current tip;
2280 defaults to 30 days.
2281 </p>
2282 </dd>
2283 <dt>
2284 gc.rerereresolved
2285 </dt>
2286 <dd>
2287 <p>
2288 Records of conflicted merge you resolved earlier are
2291 </p>
2292 </dd>
2293 <dt>
2294 gc.rerereunresolved
2295 </dt>
2296 <dd>
2297 <p>
2298 Records of conflicted merge you have not resolved are
2301 </p>
2302 </dd>
2303 <dt>
2304 gitcvs.commitmsgannotation
2305 </dt>
2306 <dd>
2307 <p>
2308 Append this string to each commit message. Set to empty string
2309 to disable this feature. Defaults to "via git-CVS emulator".
2310 </p>
2311 </dd>
2312 <dt>
2313 gitcvs.enabled
2314 </dt>
2315 <dd>
2316 <p>
2317 Whether the CVS server interface is enabled for this repository.
2319 </p>
2320 </dd>
2321 <dt>
2322 gitcvs.logfile
2323 </dt>
2324 <dd>
2325 <p>
2326 Path to a log file where the CVS server interface well… logs
2328 </p>
2329 </dd>
2330 <dt>
2331 gitcvs.usecrlfattr
2332 </dt>
2333 <dd>
2334 <p>
2342 </p>
2343 </dd>
2344 <dt>
2345 gitcvs.allbinary
2346 </dt>
2347 <dd>
2348 <p>
2351 unresolved files are sent to the client in
2353 as binary files, which suppresses any newline munging it
2354 otherwise might do. Alternatively, if it is set to "guess",
2355 then the contents of the file are examined to decide if
2357 </p>
2358 </dd>
2359 <dt>
2360 gitcvs.dbname
2361 </dt>
2362 <dd>
2363 <p>
2364 Database used by git-cvsserver to cache revision information
2365 derived from the git repository. The exact meaning depends on the
2366 used database driver, for SQLite (which is the default driver) this
2367 is a filename. Supports variable substitution (see
2368 <a href="git-cvsserver.html">git-cvsserver(1)</a> for details). May not contain semicolons (<tt>;</tt>).
2370 </p>
2371 </dd>
2372 <dt>
2373 gitcvs.dbdriver
2374 </dt>
2375 <dd>
2376 <p>
2377 Used Perl DBI driver. You can specify any available driver
2378 for this here, but it might not work. git-cvsserver is tested
2383 </p>
2384 </dd>
2385 <dt>
2386 gitcvs.dbuser, gitcvs.dbpass
2387 </dt>
2388 <dd>
2389 <p>
2391 since SQLite has no concept of database users and/or passwords.
2394 </p>
2395 </dd>
2396 <dt>
2397 gitcvs.dbTableNamePrefix
2398 </dt>
2399 <dd>
2400 <p>
2401 Database table name prefix. Prepended to the names of any
2402 database tables used, allowing a single database to be used
2403 for several repositories. Supports variable substitution (see
2405 characters will be replaced with underscores.
2406 </p>
2407 </dd>
2408 </dl></div>
2413 access method.</p></div>
2415 <dt>
2416 gui.commitmsgwidth
2417 </dt>
2418 <dd>
2419 <p>
2420 Defines how wide the commit message window is in the
2422 </p>
2423 </dd>
2424 <dt>
2425 gui.diffcontext
2426 </dt>
2427 <dd>
2428 <p>
2429 Specifies how many context lines should be used in calls to diff
2431 </p>
2432 </dd>
2433 <dt>
2434 gui.encoding
2435 </dt>
2436 <dd>
2437 <p>
2438 Specifies the default encoding to use for displaying of
2442 If this option is not set, the tools default to the
2443 locale encoding.
2444 </p>
2445 </dd>
2446 <dt>
2447 gui.matchtrackingbranch
2448 </dt>
2449 <dd>
2450 <p>
2452 default to tracking remote branches with matching names or
2453 not. Default: "false".
2454 </p>
2455 </dd>
2456 <dt>
2457 gui.newbranchtemplate
2458 </dt>
2459 <dd>
2460 <p>
2461 Is used as suggested name when creating new branches using the
2463 </p>
2464 </dd>
2465 <dt>
2466 gui.pruneduringfetch
2467 </dt>
2468 <dd>
2469 <p>
2471 performing a fetch. The default value is "false".
2472 </p>
2473 </dd>
2474 <dt>
2475 gui.trustmtime
2476 </dt>
2477 <dd>
2478 <p>
2480 timestamp or not. By default the timestamps are not trusted.
2481 </p>
2482 </dd>
2483 <dt>
2484 gui.spellingdictionary
2485 </dt>
2486 <dd>
2487 <p>
2488 Specifies the dictionary used for spell checking commit messages in
2490 off.
2491 </p>
2492 </dd>
2493 <dt>
2494 gui.fastcopyblame
2495 </dt>
2496 <dd>
2497 <p>
2499 location detection. It makes blame significantly faster on huge
2500 repositories at the expense of less thorough copy detection.
2501 </p>
2502 </dd>
2503 <dt>
2504 gui.copyblamethreshold
2505 </dt>
2506 <dd>
2507 <p>
2509 detection, measured in alphanumeric characters. See the
2511 </p>
2512 </dd>
2513 <dt>
2514 gui.blamehistoryctx
2515 </dt>
2516 <dd>
2517 <p>
2518 Specifies the radius of history context in days to show in
2521 variable is set to zero, the whole history is shown.
2522 </p>
2523 </dd>
2524 <dt>
2526 </dt>
2527 <dd>
2528 <p>
2529 Specifies the shell command line to execute when the corresponding item
2531 mandatory for every tool. The command is executed from the root of
2532 the working directory, and in the environment it receives the name of
2536 </p>
2537 </dd>
2538 <dt>
2540 </dt>
2541 <dd>
2542 <p>
2543 Run the tool only if a diff is selected in the GUI. It guarantees
2545 </p>
2546 </dd>
2547 <dt>
2549 </dt>
2550 <dd>
2551 <p>
2552 Run the command silently, without creating a window to display its
2553 output.
2554 </p>
2555 </dd>
2556 <dt>
2558 </dt>
2559 <dd>
2560 <p>
2561 Don't rescan the working directory for changes after the tool
2562 finishes execution.
2563 </p>
2564 </dd>
2565 <dt>
2567 </dt>
2568 <dd>
2569 <p>
2570 Show a confirmation dialog before actually running the tool.
2571 </p>
2572 </dd>
2573 <dt>
2575 </dt>
2576 <dd>
2577 <p>
2578 Request a string argument from the user, and pass it to the tool
2582 the dialog uses a built-in generic prompt; otherwise the exact
2583 value of the variable is used.
2584 </p>
2585 </dd>
2586 <dt>
2588 </dt>
2589 <dd>
2590 <p>
2591 Request a single valid revision from the user, and set the
2594 </p>
2595 </dd>
2596 <dt>
2598 </dt>
2599 <dd>
2600 <p>
2602 This is useful for tools similar to merge or rebase, but not
2603 for things like checkout or reset.
2604 </p>
2605 </dd>
2606 <dt>
2608 </dt>
2609 <dd>
2610 <p>
2611 Specifies the title to use for the prompt dialog. The default
2612 is the tool name.
2613 </p>
2614 </dd>
2615 <dt>
2617 </dt>
2618 <dd>
2619 <p>
2620 Specifies the general prompt string to display at the top of
2622 The default value includes the actual command.
2623 </p>
2624 </dd>
2625 <dt>
2626 help.browser
2627 </dt>
2628 <dd>
2629 <p>
2630 Specify the browser that will be used to display help in the
2632 </p>
2633 </dd>
2634 <dt>
2635 help.format
2636 </dt>
2637 <dd>
2638 <p>
2640 Values <em>man</em>, <em>info</em>, <em>web</em> and <em>html</em> are supported. <em>man</em> is
2642 </p>
2643 </dd>
2644 <dt>
2645 help.autocorrect
2646 </dt>
2647 <dd>
2648 <p>
2649 Automatically correct and execute mistyped commands after
2650 waiting for the given number of deciseconds (0.1 sec). If more
2651 than one command can be deduced from the entered text, nothing
2652 will be executed. If the value of this option is negative,
2653 the corrected command will be executed immediately. If the
2654 value is 0 - the command will be just shown but not executed.
2655 This is the default.
2656 </p>
2657 </dd>
2658 <dt>
2659 http.proxy
2660 </dt>
2661 <dd>
2662 <p>
2666 </p>
2667 </dd>
2668 <dt>
2669 http.sslVerify
2670 </dt>
2671 <dd>
2672 <p>
2673 Whether to verify the SSL certificate when fetching or pushing
2675 variable.
2676 </p>
2677 </dd>
2678 <dt>
2679 http.sslCert
2680 </dt>
2681 <dd>
2682 <p>
2683 File containing the SSL certificate when fetching or pushing
2685 variable.
2686 </p>
2687 </dd>
2688 <dt>
2689 http.sslKey
2690 </dt>
2691 <dd>
2692 <p>
2693 File containing the SSL private key when fetching or pushing
2695 variable.
2696 </p>
2697 </dd>
2698 <dt>
2699 http.sslCertPasswordProtected
2700 </dt>
2701 <dd>
2702 <p>
2703 Enable git's password prompt for the SSL certificate. Otherwise
2704 OpenSSL will prompt the user, possibly many times, if the
2705 certificate or private key is encrypted. Can be overridden by the
2707 </p>
2708 </dd>
2709 <dt>
2710 http.sslCAInfo
2711 </dt>
2712 <dd>
2713 <p>
2714 File containing the certificates to verify the peer with when
2715 fetching or pushing over HTTPS. Can be overridden by the
2717 </p>
2718 </dd>
2719 <dt>
2720 http.sslCAPath
2721 </dt>
2722 <dd>
2723 <p>
2724 Path containing files with the CA certificates to verify the peer
2725 with when fetching or pushing over HTTPS. Can be overridden
2727 </p>
2728 </dd>
2729 <dt>
2730 http.maxRequests
2731 </dt>
2732 <dd>
2733 <p>
2734 How many HTTP requests to launch in parallel. Can be overridden
2736 </p>
2737 </dd>
2738 <dt>
2739 http.minSessions
2740 </dt>
2741 <dd>
2742 <p>
2743 The number of curl sessions (counted across slots) to be kept across
2744 requests. They will not be ended with curl_easy_cleanup() until
2745 http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this
2747 </p>
2748 </dd>
2749 <dt>
2750 http.postBuffer
2751 </dt>
2752 <dd>
2753 <p>
2754 Maximum size in bytes of the buffer used by smart HTTP
2755 transports when POSTing data to the remote system.
2756 For requests larger than this buffer size, HTTP/1.1 and
2757 Transfer-Encoding: chunked is used to avoid creating a
2758 massive pack file locally. Default is 1 MiB, which is
2759 sufficient for most requests.
2760 </p>
2761 </dd>
2762 <dt>
2763 http.lowSpeedLimit, http.lowSpeedTime
2764 </dt>
2765 <dd>
2766 <p>
2771 </p>
2772 </dd>
2773 <dt>
2774 http.noEPSV
2775 </dt>
2776 <dd>
2777 <p>
2778 A boolean which disables using of EPSV ftp command by curl.
2779 This can helpful with some "poor" ftp servers which don't
2781 environment variable. Default is false (curl will use EPSV).
2782 </p>
2783 </dd>
2784 <dt>
2785 i18n.commitEncoding
2786 </dt>
2787 <dd>
2788 <p>
2789 Character encoding the commit messages are stored in; git itself
2790 does not care per se, but this information is necessary e.g. when
2791 importing commits from emails or in the gitk graphical history
2792 browser (and possibly at other places in the future or in other
2793 porcelains). See e.g. <a href="git-mailinfo.html">git-mailinfo(1)</a>. Defaults to <em>utf-8</em>.
2794 </p>
2795 </dd>
2796 <dt>
2797 i18n.logOutputEncoding
2798 </dt>
2799 <dd>
2800 <p>
2801 Character encoding the commit messages are converted to when
2803 </p>
2804 </dd>
2805 <dt>
2806 imap
2807 </dt>
2808 <dd>
2809 <p>
2812 </p>
2813 </dd>
2814 <dt>
2815 init.templatedir
2816 </dt>
2817 <dd>
2818 <p>
2819 Specify the directory from which templates will be copied.
2821 </p>
2822 </dd>
2823 <dt>
2824 instaweb.browser
2825 </dt>
2826 <dd>
2827 <p>
2828 Specify the program that will be used to browse your working
2830 </p>
2831 </dd>
2832 <dt>
2833 instaweb.httpd
2834 </dt>
2835 <dd>
2836 <p>
2837 The HTTP daemon command-line to start gitweb on your working
2839 </p>
2840 </dd>
2841 <dt>
2842 instaweb.local
2843 </dt>
2844 <dd>
2845 <p>
2847 be bound to the local IP (127.0.0.1).
2848 </p>
2849 </dd>
2850 <dt>
2851 instaweb.modulepath
2852 </dt>
2853 <dd>
2854 <p>
2856 </p>
2857 </dd>
2858 <dt>
2859 instaweb.port
2860 </dt>
2861 <dd>
2862 <p>
2863 The port number to bind the gitweb httpd to. See
2865 </p>
2866 </dd>
2867 <dt>
2868 interactive.singlekey
2869 </dt>
2870 <dd>
2871 <p>
2872 In interactive commands, allow the user to provide one-letter
2873 input with a single key (i.e., without hitting enter).
2876 ignored if portable keystroke input is not available.
2877 </p>
2878 </dd>
2879 <dt>
2880 log.date
2881 </dt>
2882 <dd>
2883 <p>
2884 Set default date-time mode for the log command. Setting log.date
2886 following alternatives: {relative,local,default,iso,rfc,short}.
2888 </p>
2889 </dd>
2890 <dt>
2891 log.showroot
2892 </dt>
2893 <dd>
2894 <p>
2895 If true, the initial commit will be shown as a big creation event.
2896 This is equivalent to a diff against an empty tree.
2897 Tools like <a href="git-log.html">git-log(1)</a> or <a href="git-whatchanged.html">git-whatchanged(1)</a>, which
2898 normally hide the root commit will now show it. True by default.
2899 </p>
2900 </dd>
2901 <dt>
2902 mailmap.file
2903 </dt>
2904 <dd>
2905 <p>
2906 The location of an augmenting mailmap file. The default
2907 mailmap, located in the root of the repository, is loaded
2908 first, then the mailmap file pointed to by this variable.
2909 The location of the mailmap file may be in a repository
2910 subdirectory, or somewhere outside of the repository itself.
2911 See <a href="git-shortlog.html">git-shortlog(1)</a> and <a href="git-blame.html">git-blame(1)</a>.
2912 </p>
2913 </dd>
2914 <dt>
2915 man.viewer
2916 </dt>
2917 <dd>
2918 <p>
2919 Specify the programs that may be used to display help in the
2921 </p>
2922 </dd>
2923 <dt>
2925 </dt>
2926 <dd>
2927 <p>
2928 Specify the command to invoke the specified man viewer. The
2929 specified command is evaluated in shell with the man page
2931 </p>
2932 </dd>
2933 <dt>
2935 </dt>
2936 <dd>
2937 <p>
2938 Override the path for the given tool that may be used to
2940 </p>
2941 </dd>
2942 <dt>
2943 merge.conflictstyle
2944 </dt>
2945 <dd>
2946 <p>
2947 Specify the style in which conflicted hunks are written out to
2948 working tree files upon merge. The default is "merge", which
2951 a <tt>>>>>>>></tt> marker. An alternate style, "diff3", adds a <tt>|||||||</tt>
2953 </p>
2954 </dd>
2955 <dt>
2956 merge.log
2957 </dt>
2958 <dd>
2959 <p>
2960 Whether to include summaries of merged commits in newly created
2961 merge commit messages. False by default.
2962 </p>
2963 </dd>
2964 <dt>
2965 merge.renameLimit
2966 </dt>
2967 <dd>
2968 <p>
2969 The number of files to consider when performing rename detection
2970 during a merge; if not specified, defaults to the value of
2971 diff.renameLimit.
2972 </p>
2973 </dd>
2974 <dt>
2975 merge.stat
2976 </dt>
2977 <dd>
2978 <p>
2979 Whether to print the diffstat between ORIG_HEAD and the merge result
2980 at the end of the merge. True by default.
2981 </p>
2982 </dd>
2983 <dt>
2984 merge.tool
2985 </dt>
2986 <dd>
2987 <p>
2988 Controls which merge resolution program is used by
2992 "opendiff". Any other value is treated is custom merge tool
2994 </p>
2995 </dd>
2996 <dt>
2997 merge.verbosity
2998 </dt>
2999 <dd>
3000 <p>
3001 Controls the amount of output shown by the recursive merge
3002 strategy. Level 0 outputs nothing except a final error
3003 message if conflicts were detected. Level 1 outputs only
3005 above outputs debugging information. The default is level 2.
3007 </p>
3008 </dd>
3009 <dt>
3011 </dt>
3012 <dd>
3013 <p>
3014 Defines a human-readable name for a custom low-level
3016 </p>
3017 </dd>
3018 <dt>
3020 </dt>
3021 <dd>
3022 <p>
3023 Defines the command that implements a custom low-level
3025 </p>
3026 </dd>
3027 <dt>
3029 </dt>
3030 <dd>
3031 <p>
3032 Names a low-level merge driver to be used when
3033 performing an internal merge between common ancestors.
3035 </p>
3036 </dd>
3037 <dt>
3039 </dt>
3040 <dd>
3041 <p>
3042 Override the path for the given tool. This is useful in case
3043 your tool is not in the PATH.
3044 </p>
3045 </dd>
3046 <dt>
3048 </dt>
3049 <dd>
3050 <p>
3051 Specify the command to invoke the specified merge tool. The
3052 specified command is evaluated in shell with the following
3054 containing the common base of the files to be merged, if available;
3057 file containing the contents of the file from the branch being
3059 tool should write the results of a successful merge.
3060 </p>
3061 </dd>
3062 <dt>
3064 </dt>
3065 <dd>
3066 <p>
3067 For a custom merge command, specify whether the exit code of
3068 the merge command can be used to determine whether the merge was
3069 successful. If this is not set to true then the merge target file
3070 timestamp is checked and the merge assumed to have been successful
3071 if the file has been updated, otherwise the user is prompted to
3072 indicate the success of the merge.
3073 </p>
3074 </dd>
3075 <dt>
3076 mergetool.keepBackup
3077 </dt>
3078 <dd>
3079 <p>
3080 After performing a merge, the original file with conflict markers
3084 </p>
3085 </dd>
3086 <dt>
3087 mergetool.keepTemporaries
3088 </dt>
3089 <dd>
3090 <p>
3091 When invoking a custom merge tool, git uses a set of temporary
3092 files to pass to the tool. If the tool returns an error and this
3094 preserved, otherwise they will be removed after the tool has
3096 </p>
3097 </dd>
3098 <dt>
3099 mergetool.prompt
3100 </dt>
3101 <dd>
3102 <p>
3103 Prompt before each invocation of the merge resolution program.
3104 </p>
3105 </dd>
3106 <dt>
3107 notes.displayRef
3108 </dt>
3109 <dd>
3110 <p>
3111 The (fully qualified) refname from which to show notes when
3112 showing commit messages. The value of this variable can be set
3113 to a glob, in which case notes from all matching refs will be
3114 shown. You may also specify this configuration variable
3115 several times. A warning will be issued for refs that do not
3116 exist, but a glob that does not match any refs is silently
3117 ignored.
3118 </p>
3120 environment variable, which must be a colon separated list of refs or
3121 globs.</p></div>
3123 GIT_NOTES_REF) is also implicitly added to the list of refs to be
3124 displayed.</p></div>
3125 </dd>
3126 <dt>
3128 </dt>
3129 <dd>
3130 <p>
3133 automatically copies your notes from the original to the
3135 "notes.rewriteRef" below.
3136 </p>
3138 environment variable, which must be a colon separated list of refs or
3139 globs.</p></div>
3140 </dd>
3141 <dt>
3142 notes.rewriteMode
3143 </dt>
3144 <dd>
3145 <p>
3146 When copying notes during a rewrite (see the
3147 "notes.rewrite.<command>" option), determines what to do if
3148 the target commit already has a note. Must be one of
3151 </p>
3153 environment variable.</p></div>
3154 </dd>
3155 <dt>
3156 notes.rewriteRef
3157 </dt>
3158 <dd>
3159 <p>
3160 When copying notes during a rewrite, specifies the (fully
3161 qualified) ref whose notes should be copied. The ref may be a
3162 glob, in which case notes in all matching refs will be copied.
3163 You may also specify this configuration several times.
3164 </p>
3166 enable note rewriting.</p></div>
3167 </dd>
3168 <dt>
3169 pack.window
3170 </dt>
3171 <dd>
3172 <p>
3174 window size is given on the command line. Defaults to 10.
3175 </p>
3176 </dd>
3177 <dt>
3178 pack.depth
3179 </dt>
3180 <dd>
3181 <p>
3182 The maximum delta depth used by <a href="git-pack-objects.html">git-pack-objects(1)</a> when no
3183 maximum depth is given on the command line. Defaults to 50.
3184 </p>
3185 </dd>
3186 <dt>
3187 pack.windowMemory
3188 </dt>
3189 <dd>
3190 <p>
3192 when no limit is given on the command line. The value can be
3194 limit.
3195 </p>
3196 </dd>
3197 <dt>
3198 pack.compression
3199 </dt>
3200 <dd>
3201 <p>
3205 slowest. If not set, defaults to core.compression. If that is
3207 compromise between speed and compression (currently equivalent
3208 to level 6)."
3209 </p>
3210 </dd>
3211 <dt>
3212 pack.deltaCacheSize
3213 </dt>
3214 <dd>
3215 <p>
3216 The maximum memory in bytes used for caching deltas in
3218 This cache is used to speed up the writing object phase by not
3219 having to recompute the final delta result once the best match
3220 for all objects is found. Repacking large repositories on machines
3221 which are tight with memory might be badly impacted by this though,
3222 especially if this cache pushes the system into swapping.
3224 used to virtually disable this cache. Defaults to 256 MiB.
3225 </p>
3226 </dd>
3227 <dt>
3228 pack.deltaCacheLimit
3229 </dt>
3230 <dd>
3231 <p>
3232 The maximum size of a delta, that is cached in
3234 writing object phase by not having to recompute the final delta
3235 result once the best match for all objects is found. Defaults to 1000.
3236 </p>
3237 </dd>
3238 <dt>
3239 pack.threads
3240 </dt>
3241 <dd>
3242 <p>
3243 Specifies the number of threads to spawn when searching for best
3245 be compiled with pthreads otherwise this option is ignored with a
3246 warning. This is meant to reduce packing time on multiprocessor
3247 machines. The required amount of memory for the delta search window
3248 is however multiplied by the number of threads.
3249 Specifying 0 will cause git to auto-detect the number of CPU's
3250 and set the number of threads accordingly.
3251 </p>
3252 </dd>
3253 <dt>
3254 pack.indexVersion
3255 </dt>
3256 <dd>
3257 <p>
3258 Specify the default pack index version. Valid values are 1 for
3260 the new pack index with capabilities for packs larger than 4 GB
3261 as well as proper protection against the repacking of corrupted
3263 and this config option ignored whenever the corresponding pack is
3264 larger than 2 GB.
3265 </p>
3266 <div class="para"><p>If you have an old git that does not understand the version 2 <tt>*.idx</tt> file,
3268 that will copy both <tt>*.pack</tt> file and corresponding <tt>*.idx</tt> file from the
3269 other side may give you a repository that cannot be accessed with your
3271 you can use <a href="git-index-pack.html">git-index-pack(1)</a> on the *.pack file to regenerate
3273 </dd>
3274 <dt>
3275 pack.packSizeLimit
3276 </dt>
3277 <dd>
3278 <p>
3279 The maximum size of a pack. This setting only affects
3280 packing to a file when repacking, i.e. the git:// protocol
3283 limited to 1 MiB. The default is unlimited.
3285 supported.
3286 </p>
3287 </dd>
3288 <dt>
3290 </dt>
3291 <dd>
3292 <p>
3293 Allows turning on or off pagination of the output of a
3294 particular git subcommand when writing to a tty. If
3296 it takes precedence over this option. To disable pagination for
3298 </p>
3299 </dd>
3300 <dt>
3301 pull.octopus
3302 </dt>
3303 <dd>
3304 <p>
3305 The default merge strategy to use when pulling multiple branches
3306 at once.
3307 </p>
3308 </dd>
3309 <dt>
3310 pull.twohead
3311 </dt>
3312 <dd>
3313 <p>
3314 The default merge strategy to use when pulling a single branch.
3315 </p>
3316 </dd>
3317 <dt>
3318 push.default
3319 </dt>
3320 <dd>
3321 <p>
3322 Defines the action git push should take if no refspec is given
3323 on the command line, no refspec is configured in the remote, and
3324 no refspec is implied by any of the options given on the command
3325 line. Possible values are:
3326 </p>
3328 <li>
3329 <p>
3331 </p>
3332 </li>
3333 <li>
3334 <p>
3336 All branches having the same name in both ends are considered to be
3337 matching. This is the default.
3338 </p>
3339 </li>
3340 <li>
3341 <p>
3343 </p>
3344 </li>
3345 <li>
3346 <p>
3348 </p>
3349 </li>
3350 </ul></div>
3351 </dd>
3352 <dt>
3353 rebase.stat
3354 </dt>
3355 <dd>
3356 <p>
3357 Whether to show a diffstat of what changed upstream since the last
3358 rebase. False by default.
3359 </p>
3360 </dd>
3361 <dt>
3362 receive.autogc
3363 </dt>
3364 <dd>
3365 <p>
3366 By default, git-receive-pack will run "git-gc --auto" after
3367 receiving data from git-push and updating refs. You can stop
3368 it by setting this variable to false.
3369 </p>
3370 </dd>
3371 <dt>
3372 receive.fsckObjects
3373 </dt>
3374 <dd>
3375 <p>
3376 If it is set to true, git-receive-pack will check all received
3377 objects. It will abort in the case of a malformed object or a
3378 broken link. The result of an abort are only dangling objects.
3379 Defaults to false.
3380 </p>
3381 </dd>
3382 <dt>
3383 receive.unpackLimit
3384 </dt>
3385 <dd>
3386 <p>
3387 If the number of objects received in a push is below this
3388 limit then the objects will be unpacked into loose object
3389 files. However if the number of received objects equals or
3390 exceeds this limit then the received pack will be stored as
3391 a pack, after adding any missing delta bases. Storing the
3392 pack from a push can make the push operation complete faster,
3393 especially on slow filesystems. If not set, the value of
3395 </p>
3396 </dd>
3397 <dt>
3398 receive.denyDeletes
3399 </dt>
3400 <dd>
3401 <p>
3402 If set to true, git-receive-pack will deny a ref update that deletes
3403 the ref. Use this to prevent such a ref deletion via a push.
3404 </p>
3405 </dd>
3406 <dt>
3407 receive.denyCurrentBranch
3408 </dt>
3409 <dd>
3410 <p>
3411 If set to true or "refuse", receive-pack will deny a ref update
3412 to the currently checked out branch of a non-bare repository.
3413 Such a push is potentially dangerous because it brings the HEAD
3414 out of sync with the index and working tree. If set to "warn",
3415 print a warning of such a push to stderr, but allow the push to
3416 proceed. If set to false or "ignore", allow such pushes with no
3417 message. Defaults to "refuse".
3418 </p>
3419 </dd>
3420 <dt>
3421 receive.denyNonFastForwards
3422 </dt>
3423 <dd>
3424 <p>
3425 If set to true, git-receive-pack will deny a ref update which is
3426 not a fast-forward. Use this to prevent such an update via a push,
3427 even if that push is forced. This configuration variable is
3428 set when initializing a shared repository.
3429 </p>
3430 </dd>
3431 <dt>
3432 receive.updateserverinfo
3433 </dt>
3434 <dd>
3435 <p>
3436 If set to true, git-receive-pack will run git-update-server-info
3437 after receiving data from git-push and updating refs.
3438 </p>
3439 </dd>
3440 <dt>
3442 </dt>
3443 <dd>
3444 <p>
3447 </p>
3448 </dd>
3449 <dt>
3451 </dt>
3452 <dd>
3453 <p>
3455 </p>
3456 </dd>
3457 <dt>
3459 </dt>
3460 <dd>
3461 <p>
3462 For remotes that require curl (http, https and ftp), the URL to
3463 the proxy to use for that remote. Set to the empty string to
3464 disable proxying for that remote.
3465 </p>
3466 </dd>
3467 <dt>
3469 </dt>
3470 <dd>
3471 <p>
3474 </p>
3475 </dd>
3476 <dt>
3478 </dt>
3479 <dd>
3480 <p>
3483 </p>
3484 </dd>
3485 <dt>
3487 </dt>
3488 <dd>
3489 <p>
3490 If true, pushing to this remote will automatically behave
3492 </p>
3493 </dd>
3494 <dt>
3496 </dt>
3497 <dd>
3498 <p>
3499 If true, this remote will be skipped by default when updating
3502 </p>
3503 </dd>
3504 <dt>
3506 </dt>
3507 <dd>
3508 <p>
3509 If true, this remote will be skipped by default when updating
3512 </p>
3513 </dd>
3514 <dt>
3516 </dt>
3517 <dd>
3518 <p>
3519 The default program to execute on the remote side when pushing. See
3521 </p>
3522 </dd>
3523 <dt>
3525 </dt>
3526 <dd>
3527 <p>
3528 The default program to execute on the remote side when fetching. See
3530 </p>
3531 </dd>
3532 <dt>
3534 </dt>
3535 <dd>
3536 <p>
3537 Setting this value to --no-tags disables automatic tag following when
3539 </p>
3540 </dd>
3541 <dt>
3543 </dt>
3544 <dd>
3545 <p>
3548 </p>
3549 </dd>
3550 <dt>
3552 </dt>
3553 <dd>
3554 <p>
3555 The list of remotes which are fetched by "git remote update
3557 </p>
3558 </dd>
3559 <dt>
3560 repack.usedeltabaseoffset
3561 </dt>
3562 <dd>
3563 <p>
3565 delta-base offset. If you need to share your repository with
3566 git older than version 1.4.4, either directly or via a dumb
3567 protocol such as http, then you need to set this option to
3568 "false" and repack. Access from old git versions over the
3569 native protocol are unaffected by this option.
3570 </p>
3571 </dd>
3572 <dt>
3573 rerere.autoupdate
3574 </dt>
3575 <dd>
3576 <p>
3578 resulting contents after it cleanly resolves conflicts using
3579 previously recorded resolution. Defaults to false.
3580 </p>
3581 </dd>
3582 <dt>
3583 rerere.enabled
3584 </dt>
3585 <dd>
3586 <p>
3587 Activate recording of resolved conflicts, so that identical
3588 conflict hunks can be resolved automatically, should they
3592 </p>
3593 </dd>
3594 <dt>
3595 sendemail.identity
3596 </dt>
3597 <dd>
3598 <p>
3599 A configuration identity. When given, causes values in the
3603 </p>
3604 </dd>
3605 <dt>
3606 sendemail.smtpencryption
3607 </dt>
3608 <dd>
3609 <p>
3612 </p>
3613 </dd>
3614 <dt>
3615 sendemail.smtpssl
3616 </dt>
3617 <dd>
3618 <p>
3620 </p>
3621 </dd>
3622 <dt>
3624 </dt>
3625 <dd>
3626 <p>
3628 found below, taking precedence over those when the this
3629 identity is selected, through command-line or
3631 </p>
3632 </dd>
3633 <dt>
3634 sendemail.aliasesfile
3635 </dt>
3636 <dt>
3637 sendemail.aliasfiletype
3638 </dt>
3639 <dt>
3640 sendemail.bcc
3641 </dt>
3642 <dt>
3643 sendemail.cc
3644 </dt>
3645 <dt>
3646 sendemail.cccmd
3647 </dt>
3648 <dt>
3649 sendemail.chainreplyto
3650 </dt>
3651 <dt>
3652 sendemail.confirm
3653 </dt>
3654 <dt>
3655 sendemail.envelopesender
3656 </dt>
3657 <dt>
3658 sendemail.from
3659 </dt>
3660 <dt>
3661 sendemail.multiedit
3662 </dt>
3663 <dt>
3664 sendemail.signedoffbycc
3665 </dt>
3666 <dt>
3667 sendemail.smtppass
3668 </dt>
3669 <dt>
3670 sendemail.suppresscc
3671 </dt>
3672 <dt>
3673 sendemail.suppressfrom
3674 </dt>
3675 <dt>
3676 sendemail.to
3677 </dt>
3678 <dt>
3679 sendemail.smtpserver
3680 </dt>
3681 <dt>
3682 sendemail.smtpserverport
3683 </dt>
3684 <dt>
3685 sendemail.smtpuser
3686 </dt>
3687 <dt>
3688 sendemail.thread
3689 </dt>
3690 <dt>
3691 sendemail.validate
3692 </dt>
3693 <dd>
3694 <p>
3696 </p>
3697 </dd>
3698 <dt>
3699 sendemail.signedoffcc
3700 </dt>
3701 <dd>
3702 <p>
3704 </p>
3705 </dd>
3706 <dt>
3707 showbranch.default
3708 </dt>
3709 <dd>
3710 <p>
3713 </p>
3714 </dd>
3715 <dt>
3716 status.relativePaths
3717 </dt>
3718 <dd>
3719 <p>
3722 relative to the repository root (this was the default for git
3723 prior to v1.5.4).
3724 </p>
3725 </dd>
3726 <dt>
3727 status.showUntrackedFiles
3728 </dt>
3729 <dd>
3730 <p>
3731 By default, <a href="git-status.html">git-status(1)</a> and <a href="git-commit.html">git-commit(1)</a> show
3732 files which are not currently tracked by Git. Directories which
3733 contain only untracked files, are shown with the directory name
3734 only. Showing untracked files means that Git needs to lstat() all
3735 all the files in the whole repository, which might be slow on some
3736 systems. So, this variable controls how the commands displays
3737 the untracked files. Possible values are:
3738 </p>
3740 <li>
3741 <p>
3743 </p>
3744 </li>
3745 <li>
3746 <p>
3748 </p>
3749 </li>
3750 <li>
3751 <p>
3753 </p>
3754 </li>
3755 </ul></div>
3757 This variable can be overridden with the -u|--untracked-files option
3758 of <a href="git-status.html">git-status(1)</a> and <a href="git-commit.html">git-commit(1)</a>.</p></div>
3759 </dd>
3760 <dt>
3761 tar.umask
3762 </dt>
3763 <dd>
3764 <p>
3765 This variable can be used to restrict the permission bits of
3766 tar archive entries. The default is 0002, which turns off the
3767 world write bit. The special value "user" indicates that the
3768 archiving user's umask will be used instead. See umask(2) and
3770 </p>
3771 </dd>
3772 <dt>
3773 transfer.unpackLimit
3774 </dt>
3775 <dd>
3776 <p>
3778 not set, the value of this variable is used instead.
3779 The default value is 100.
3780 </p>
3781 </dd>
3782 <dt>
3784 </dt>
3785 <dd>
3786 <p>
3787 Any URL that starts with this value will be rewritten to
3789 large number of repositories, and serves them with multiple
3790 access methods, and some users need to use different access
3791 methods, this feature allows people to specify any of the
3792 equivalent URLs and have git automatically rewrite the URL to
3793 the best alternative for the particular user, even for a
3794 never-before-seen repository on the site. When more than one
3795 insteadOf strings match a given URL, the longest match is used.
3796 </p>
3797 </dd>
3798 <dt>
3800 </dt>
3801 <dd>
3802 <p>
3803 Any URL that starts with this value will not be pushed to;
3805 resulting URL will be pushed to. In cases where some site serves
3806 a large number of repositories, and serves them with multiple
3807 access methods, some of which do not allow push, this feature
3808 allows people to specify a pull-only URL and have git
3809 automatically use an appropriate URL to push, even for a
3810 never-before-seen repository on the site. When more than one
3811 pushInsteadOf strings match a given URL, the longest match is
3812 used. If a remote has an explicit pushurl, git will ignore this
3813 setting for that remote.
3814 </p>
3815 </dd>
3816 <dt>
3817 user.email
3818 </dt>
3819 <dd>
3820 <p>
3821 Your email address to be recorded in any newly created commits.
3823 <em>EMAIL</em> environment variables. See <a href="git-commit-tree.html">git-commit-tree(1)</a>.
3824 </p>
3825 </dd>
3826 <dt>
3827 user.name
3828 </dt>
3829 <dd>
3830 <p>
3831 Your full name to be recorded in any newly created commits.
3834 </p>
3835 </dd>
3836 <dt>
3837 user.signingkey
3838 </dt>
3839 <dd>
3840 <p>
3842 automatically when creating a signed tag, you can override the
3843 default selection with this variable. This option is passed
3844 unchanged to gpg's --local-user parameter, so you may specify a key
3845 using any method that gpg supports.
3846 </p>
3847 </dd>
3848 <dt>
3849 web.browser
3850 </dt>
3851 <dd>
3852 <p>
3853 Specify a web browser that may be used by some commands.
3854 Currently only <a href="git-instaweb.html">git-instaweb(1)</a> and <a href="git-help.html">git-help(1)</a>
3855 may use it.
3856 </p>
3857 </dd>
3858 </dl></div>
3859 </div>
3862 <div class="para"><p>Written by Johannes Schindelin <Johannes.Schindelin@gmx.de></p></div>
3863 </div>
3866 <div class="para"><p>Documentation by Johannes Schindelin, Petr Baudis and the git-list <git@vger.kernel.org>.</p></div>
3867 </div>
3871 </div>
3875 </div>
3876 </div>
3877 </body>
3878 </html>