| blob | c71b40249e35f72592194f094cb6fde4c2f5f816 |
4 <head>
9 /* Debug borders */
11 /*
12 border: 1px solid red;
13 */
14 }
16 body {
18 }
20 a {
23 }
26 }
28 em {
31 }
33 strong {
36 }
38 tt {
40 }
48 }
52 }
53 h2 {
55 }
56 h3 {
58 }
59 h3 + * {
61 }
66 }
68 hr {
70 }
72 p {
75 }
79 }
81 pre {
84 }
86 span#author {
91 }
92 span#email {
93 }
96 }
98 div#footer {
104 }
105 div#footer-text {
108 }
109 div#footer-badges {
112 }
114 div#preamble {
117 }
123 }
127 }
131 }
133 /* Block element titles. */
141 }
144 }
148 }
151 }
154 }
160 }
166 }
171 }
175 }
180 }
183 }
187 }
188 /* DEPRECATED: Pre version 8.2.7 verse style literal block. */
191 }
200 }
204 }
209 }
215 dl {
218 }
219 dt {
224 }
227 }
231 }
234 }
237 }
240 }
243 }
246 }
253 }
257 }
258 thead {
261 }
262 tfoot {
264 }
267 }
270 }
271 /* Because the table frame attribute is overriden by CSS in most browsers. */
274 }
278 }
282 }
288 }
291 }
294 }
300 }
303 }
307 }
311 }
315 }
317 div#toctitle {
324 }
329 }
333 }
337 }
341 }
342 /* Overrides for manpage documents */
343 h1 {
348 }
349 h2 {
351 }
354 }
358 }
360 /* Workarounds for IE6's broken and incomplete CSS2. */
366 }
373 }
379 }
384 }
388 }
392 }
397 }
399 /* IE6 sets dynamically generated links as visited. */
401 </style>
402 </head>
403 <body>
405 <h1>
406 git-config(1) Manual Page
407 </h1>
410 <p>git-config -
411 Get and set repository or global options
412 </p>
413 </div>
414 </div>
418 <div class="verseblock-content"><em>git config</em> [<file-option>] [type] [-z|--null] name [value [value_regex]]
423 <em>git config</em> [<file-option>] [type] [-z|--null] --get-regexp name_regex [value_regex]
433 </div></div>
434 </div>
437 <div class="paragraph"><p>You can query/set/replace/unset options with this command. The name is
438 actually the section and the key separated by a dot, and the value will be
439 escaped.</p></div>
440 <div class="paragraph"><p>Multiple lines can be added to an option by using the <em>--add</em> option.
441 If you want to update or unset an option which can occur on multiple
443 existing values that match the regexp are updated or unset. If
445 prepend a single exclamation mark in front (see also <a href="#EXAMPLES">[EXAMPLES]</a>).</p></div>
446 <div class="paragraph"><p>The type specifier can be either <em>--int</em> or <em>--bool</em>, to make
448 convert the value to the canonical form (simple decimal number for int,
451 checks or transformations are performed on the value.</p></div>
452 <div class="paragraph"><p>The file-option can be one of <em>--system</em>, <em>--global</em> or <em>--file</em>
453 which specify where the values will be read from or written to.
454 The default is to assume the config file of the current repository,
455 .git/config unless defined otherwise with GIT_DIR and GIT_CONFIG
459 <li>
460 <p>
461 The config file is invalid,
462 </p>
463 </li>
464 <li>
465 <p>
466 Can not write to the config file,
467 </p>
468 </li>
469 <li>
470 <p>
471 no section was provided,
472 </p>
473 </li>
474 <li>
475 <p>
476 the section or key is invalid,
477 </p>
478 </li>
479 <li>
480 <p>
481 you try to unset an option which does not exist,
482 </p>
483 </li>
484 <li>
485 <p>
486 you try to unset/set an option for which multiple lines match, or
487 </p>
488 </li>
489 <li>
490 <p>
492 </p>
493 </li>
494 </ol></div>
495 </div>
500 --replace-all
501 </dt>
502 <dd>
503 <p>
504 Default behavior is to replace at most one line. This replaces
505 all lines matching the key (and optionally the value_regex).
506 </p>
507 </dd>
509 --add
510 </dt>
511 <dd>
512 <p>
513 Adds a new line to the option without altering any existing
516 </p>
517 </dd>
519 --get
520 </dt>
521 <dd>
522 <p>
523 Get the value for a given key (optionally filtered by a regex
524 matching the value). Returns error code 1 if the key was not
525 found and error code 2 if multiple key values were found.
526 </p>
527 </dd>
529 --get-all
530 </dt>
531 <dd>
532 <p>
533 Like get, but does not fail if the number of values for the key
534 is not exactly one.
535 </p>
536 </dd>
538 --get-regexp
539 </dt>
540 <dd>
541 <p>
542 Like --get-all, but interprets the name as a regular expression.
543 Also outputs the key names.
544 </p>
545 </dd>
547 --global
548 </dt>
549 <dd>
550 <p>
551 For writing options: write to global ~/.gitconfig file rather than
552 the repository .git/config.
553 </p>
555 from all available files.</p></div>
557 </dd>
559 --system
560 </dt>
561 <dd>
562 <p>
563 For writing options: write to system-wide $(prefix)/etc/gitconfig
564 rather than the repository .git/config.
565 </p>
566 <div class="paragraph"><p>For reading options: read only from system-wide $(prefix)/etc/gitconfig
567 rather than from all available files.</p></div>
569 </dd>
571 -f config-file
572 </dt>
574 --file config-file
575 </dt>
576 <dd>
577 <p>
578 Use the given config file instead of the one specified by GIT_CONFIG.
579 </p>
580 </dd>
582 --remove-section
583 </dt>
584 <dd>
585 <p>
586 Remove the given section from the configuration file.
587 </p>
588 </dd>
590 --rename-section
591 </dt>
592 <dd>
593 <p>
594 Rename the given section to a new name.
595 </p>
596 </dd>
598 --unset
599 </dt>
600 <dd>
601 <p>
602 Remove the line matching the key from config file.
603 </p>
604 </dd>
606 --unset-all
607 </dt>
608 <dd>
609 <p>
610 Remove all lines matching the key from config file.
611 </p>
612 </dd>
614 -l
615 </dt>
617 --list
618 </dt>
619 <dd>
620 <p>
621 List all variables set in config file.
622 </p>
623 </dd>
625 --bool
626 </dt>
627 <dd>
628 <p>
630 </p>
631 </dd>
633 --int
634 </dt>
635 <dd>
636 <p>
639 in the config file will cause the value to be multiplied
641 </p>
642 </dd>
644 --bool-or-int
645 </dt>
646 <dd>
647 <p>
649 either --bool or --int, as described above.
650 </p>
651 </dd>
653 --path
654 </dt>
655 <dd>
656 <p>
659 specified user. This option has no effect when setting the
661 command line to let your shell do the expansion).
662 </p>
663 </dd>
665 -z
666 </dt>
668 --null
669 </dt>
670 <dd>
671 <p>
672 For all options that output values and/or keys, always
673 end values with the null character (instead of a
674 newline). Use newline instead as a delimiter between
675 key and value. This allows for secure parsing of the
676 output without getting confused e.g. by values that
677 contain line breaks.
678 </p>
679 </dd>
681 --get-colorbool name [stdout-is-tty]
682 </dt>
683 <dd>
684 <p>
687 "false", and is taken into account when configuration says
689 output of the command itself, and exits with status 0 if color
690 is to be used, or exits with status 1 otherwise.
693 </p>
694 </dd>
696 --get-color name [default]
697 </dt>
698 <dd>
699 <p>
701 output it as the ANSI color escape sequence to the standard
704 </p>
705 </dd>
707 -e
708 </dt>
710 --edit
711 </dt>
712 <dd>
713 <p>
714 Opens an editor to modify the specified config file; either
716 </p>
717 </dd>
718 </dl></div>
719 </div>
722 <div class="paragraph"><p>If not set explicitly with <em>--file</em>, there are three files where
726 $GIT_DIR/config
727 </dt>
728 <dd>
729 <p>
730 Repository specific configuration file. (The filename is
731 of course relative to the repository root, not the working
732 directory.)
733 </p>
734 </dd>
736 ~/.gitconfig
737 </dt>
738 <dd>
739 <p>
740 User-specific configuration file. Also called "global"
741 configuration file.
742 </p>
743 </dd>
745 $(prefix)/etc/gitconfig
746 </dt>
747 <dd>
748 <p>
749 System-wide configuration file.
750 </p>
751 </dd>
752 </dl></div>
753 <div class="paragraph"><p>If no further options are given, all reading options will read all of these
754 files that are available. If the global or the system-wide configuration
755 file are not available they will be ignored. If the repository configuration
757 error code. However, in neither case will an error message be issued.</p></div>
760 and <em>--unset</em>. <strong><em>git config</em> will only ever change one file at a time</strong>.</p></div>
761 <div class="paragraph"><p>You can override these rules either by command line options or by environment
763 to the global or system-wide file respectively. The GIT_CONFIG environment
764 variable has a similar effect, but you can specify any filename you want.</p></div>
765 </div>
770 GIT_CONFIG
771 </dt>
772 <dd>
773 <p>
774 Take the configuration from the given file instead of .git/config.
775 Using the "--global" option forces this to ~/.gitconfig. Using the
776 "--system" option forces this to $(prefix)/etc/gitconfig.
777 </p>
778 </dd>
779 </dl></div>
781 </div>
787 <pre><tt>#
788 # This is the config file, and
789 # a '#' or ';' character indicates
790 # a comment
791 #</tt></pre>
792 </div></div>
795 <pre><tt>; core variables
796 [core]
797 ; Don't trust file modes
798 filemode = false</tt></pre>
799 </div></div>
802 <pre><tt>; Our diff algorithm
803 [diff]
804 external = /usr/local/bin/diff-wrapper
805 renames = true</tt></pre>
806 </div></div>
809 <pre><tt>; Proxy settings
810 [core]
812 gitproxy=default-proxy ; for all the rest</tt></pre>
813 </div></div>
818 </div></div>
819 <div class="paragraph"><p>The hypothetical proxy command entries actually have a postfix to discern
820 what URL they apply to. Here is how to change the entry for kernel.org
825 </div></div>
826 <div class="paragraph"><p>This makes sure that only the key/value pair for kernel.org is replaced.</p></div>
831 </div></div>
832 <div class="paragraph"><p>If you want to delete an entry for a multivar (like core.gitproxy above),
833 you have to provide a regex matching the value of exactly one line.</p></div>
838 </div></div>
843 </div></div>
848 </div></div>
853 </div></div>
854 <div class="paragraph"><p>If you like to live dangerously, you can replace <strong>all</strong> core.gitproxy by a
855 new one with</p></div>
859 </div></div>
860 <div class="paragraph"><p>However, if you really only want to replace the line for the default proxy,
865 </div></div>
866 <div class="paragraph"><p>To actually match only values with an exclamation mark, you have to</p></div>
870 </div></div>
871 <div class="paragraph"><p>To add a new proxy, without altering any of the existing ones, use</p></div>
875 </div></div>
877 script:</p></div>
880 <pre><tt>#!/bin/sh
881 WS=$(git config --get-color color.diff.whitespace "blue reverse")
884 </div></div>
885 </div>
890 is used to store the configuration for that repository, and
893 can be used to store a system-wide default configuration.</p></div>
895 and the porcelains. The variables are divided into sections, wherein
896 the fully qualified variable name of the variable itself is the last
897 dot-separated segment and the section name is everything before the last
898 dot. The variable names are case-insensitive and only alphanumeric
899 characters are allowed. Some variables may appear multiple times.</p></div>
903 blank lines are ignored.</p></div>
905 the name of the section in square brackets and continues until the next
906 section begins. Section names are not case sensitive. Only alphanumeric
908 must belong to some section, which means that there must be a section
909 header before the first setting of a variable.</p></div>
910 <div class="paragraph"><p>Sections can be further divided into subsections. To begin a subsection
911 put its name in double quotes, separated by space from the section name,
912 in the section header, like in the example below:</p></div>
916 </div></div>
917 <div class="paragraph"><p>Subsection names are case sensitive and can contain any characters except
918 newline (doublequote <tt>"</tt> and backslash have to be escaped as <tt>\"</tt> and <tt>\\</tt>,
919 respectively). Section headers cannot span multiple
920 lines. Variables may belong directly to a section or to a given subsection.
923 <div class="paragraph"><p>There is also a case insensitive alternative <tt>[section.subsection]</tt> syntax.
924 In this syntax, subsection names follow the same restrictions as for section
925 names.</p></div>
927 header) are recognized as setting variables, in the form
930 The variable names are case-insensitive and only alphanumeric
932 for a given variable; we say then that variable is multivalued.</p></div>
934 Internal whitespace within a variable value is retained verbatim.</p></div>
935 <div class="paragraph"><p>The values following the equals sign in variable assign are all either
936 a string, an integer, or a boolean. Boolean values may be given as yes/no,
941 You need to enclose variable values in double quotes if you want to
942 preserve leading or trailing whitespace, or if the variable value contains
946 <div class="paragraph"><p>The following escape sequences (beside <tt>\"</tt> and <tt>\\</tt>) are recognized:
949 char sequences are valid.</p></div>
950 <div class="paragraph"><p>Variable values ending in a <tt>\</tt> are continued on the next line in the
951 customary UNIX fashion.</p></div>
956 <pre><tt># Core variables
957 [core]
958 ; Don't trust file modes
959 filemode = false</tt></pre>
960 </div></div>
963 <pre><tt># Our diff algorithm
964 [diff]
965 external = /usr/local/bin/diff-wrapper
966 renames = true</tt></pre>
967 </div></div>
971 remote = origin
972 merge = refs/heads/devel</tt></pre>
973 </div></div>
976 <pre><tt># Proxy settings
977 [core]
979 gitProxy=default-proxy ; for the rest</tt></pre>
980 </div></div>
982 <div class="paragraph"><p>Note that this list is non-comprehensive and not necessarily complete.
983 For command-specific variables, you will find a more detailed description
984 in the appropriate manual page. You will find a description of non-core
985 porcelain configuration variables in the respective porcelain documentation.</p></div>
988 advice.*
989 </dt>
990 <dd>
991 <p>
994 are:
995 </p>
998 pushNonFastForward
999 </dt>
1000 <dd>
1001 <p>
1003 non-fast-forward refs. Default: true.
1004 </p>
1005 </dd>
1007 statusHints
1008 </dt>
1009 <dd>
1010 <p>
1011 Directions on how to stage/unstage/add shown in the
1013 when writing commit messages. Default: true.
1014 </p>
1015 </dd>
1017 commitBeforeMerge
1018 </dt>
1019 <dd>
1020 <p>
1022 merge to avoid overwriting local changes.
1023 Default: true.
1024 </p>
1025 </dd>
1027 resolveConflict
1028 </dt>
1029 <dd>
1030 <p>
1031 Advices shown by various commands when conflicts
1032 prevent the operation from being performed.
1033 Default: true.
1034 </p>
1035 </dd>
1037 implicitIdentity
1038 </dt>
1039 <dd>
1040 <p>
1041 Advice on how to set your identity configuration when
1042 your information is guessed from the system username and
1043 domain name. Default: true.
1044 </p>
1045 </dd>
1047 detachedHead
1048 </dt>
1049 <dd>
1050 <p>
1052 move to the detach HEAD state, to instruct how to create
1053 a local branch after the fact. Default: true.
1054 </p>
1055 </dd>
1056 </dl></div>
1057 </dd>
1059 core.fileMode
1060 </dt>
1061 <dd>
1062 <p>
1063 If false, the executable bit differences between the index and
1064 the working copy are ignored; useful on broken filesystems like FAT.
1066 </p>
1067 <div class="paragraph"><p>The default is true, except <a href="git-clone.html">git-clone(1)</a> or <a href="git-init.html">git-init(1)</a>
1068 will probe and set core.fileMode false if appropriate when the
1069 repository is created.</p></div>
1070 </dd>
1072 core.ignoreCygwinFSTricks
1073 </dt>
1074 <dd>
1075 <p>
1076 This option is only used by Cygwin implementation of Git. If false,
1077 the Cygwin stat() and lstat() functions are used. This may be useful
1078 if your repository consists of a few separate directories joined in
1079 one hierarchy using Cygwin mount. If true, Git uses native Win32 API
1080 whenever it is possible and falls back to Cygwin functions only to
1081 handle symbol links. The native mode is more than twice faster than
1082 normal Cygwin l/stat() functions. True by default, unless core.filemode
1083 is true, in which case ignoreCygwinFSTricks is ignored as Cygwin’s
1084 POSIX emulation is required to support core.filemode.
1085 </p>
1086 </dd>
1088 core.ignorecase
1089 </dt>
1090 <dd>
1091 <p>
1092 If true, this option enables various workarounds to enable
1093 git to work better on filesystems that are not case sensitive,
1094 like FAT. For example, if a directory listing finds
1096 it is really the same file, and continue to remember it as
1097 "Makefile".
1098 </p>
1099 <div class="paragraph"><p>The default is false, except <a href="git-clone.html">git-clone(1)</a> or <a href="git-init.html">git-init(1)</a>
1100 will probe and set core.ignorecase true if appropriate when the repository
1101 is created.</p></div>
1102 </dd>
1104 core.trustctime
1105 </dt>
1106 <dd>
1107 <p>
1108 If false, the ctime differences between the index and the
1109 working copy are ignored; useful when the inode change time
1110 is regularly modified by something outside Git (file system
1111 crawlers and some backup systems).
1113 </p>
1114 </dd>
1116 core.quotepath
1117 </dt>
1118 <dd>
1119 <p>
1122 "unusual" characters in the pathname by enclosing the
1123 pathname in a double-quote pair and with backslashes the
1124 same way strings in C source code are quoted. If this
1125 variable is set to false, the bytes higher than 0x80 are
1126 not quoted but output as verbatim. Note that double
1127 quote, backslash and control characters are always
1129 variable.
1130 </p>
1131 </dd>
1133 core.eol
1134 </dt>
1135 <dd>
1136 <p>
1137 Sets the line ending type to use in the working directory for
1142 conversion.
1143 </p>
1144 </dd>
1146 core.safecrlf
1147 </dt>
1148 <dd>
1149 <p>
1151 end-of-line conversion is active. Git will verify if a command
1152 modifies a file in the work tree either directly or indirectly.
1153 For example, committing a file followed by checking out the
1154 same file should yield the original file in the work tree. If
1155 this is not the case for the current setting of
1157 be set to "warn", in which case git will only warn about an
1158 irreversible conversion but continue the operation.
1159 </p>
1161 When it is enabled, git will convert CRLF to LF during commit and LF to
1162 CRLF during checkout. A file that contains a mixture of LF and
1163 CRLF before the commit cannot be recreated by git. For text
1164 files this is the right thing to do: it corrects line endings
1165 such that we have only LF line endings in the repository.
1166 But for binary files that are accidentally classified as text the
1167 conversion can corrupt data.</p></div>
1169 setting the conversion type explicitly in .gitattributes. Right
1170 after committing you still have the original file in your work
1171 tree and this file is not yet corrupted. You can explicitly tell
1172 git that this file is binary and git will handle the file
1173 appropriately.</p></div>
1175 mixed line endings and the undesired effect of corrupting binary
1176 files cannot be distinguished. In both cases CRLFs are removed
1177 in an irreversible way. For text files this is the right thing
1178 to do because CRLFs are line endings, while for binary files
1179 converting CRLFs corrupts data.</p></div>
1180 <div class="paragraph"><p>Note, this safety check does not mean that a checkout will generate a
1181 file identical to the original file for a different setting of
1189 mechanism.</p></div>
1190 </dd>
1192 core.autocrlf
1193 </dt>
1194 <dd>
1195 <p>
1196 Setting this variable to "true" is almost the same as setting
1198 files are not guaranteed to be normalized: files that contain
1201 working directory even though the repository does not have
1203 in which case no output conversion is performed.
1204 </p>
1205 </dd>
1207 core.symlinks
1208 </dt>
1209 <dd>
1210 <p>
1211 If false, symbolic links are checked out as small plain files that
1214 file. Useful on filesystems like FAT that do not support
1215 symbolic links.
1216 </p>
1217 <div class="paragraph"><p>The default is true, except <a href="git-clone.html">git-clone(1)</a> or <a href="git-init.html">git-init(1)</a>
1218 will probe and set core.symlinks false if appropriate when the repository
1219 is created.</p></div>
1220 </dd>
1222 core.gitProxy
1223 </dt>
1224 <dd>
1225 <p>
1227 of establishing direct connection to the remote server when
1228 using the git protocol for fetching. If the variable value is
1229 in the "COMMAND for DOMAIN" format, the command is applied only
1230 on hostnames ending with the specified domain string. This variable
1231 may be set multiple times and is matched in the given order;
1232 the first match wins.
1233 </p>
1234 <div class="paragraph"><p>Can be overridden by the <em>GIT_PROXY_COMMAND</em> environment variable
1235 (which always applies universally, without the special "for"
1236 handling).</p></div>
1238 specify that no proxy be used for a given domain pattern.
1239 This is useful for excluding servers inside a firewall from
1240 proxy use, while defaulting to a common proxy for external domains.</p></div>
1241 </dd>
1243 core.ignoreStat
1244 </dt>
1245 <dd>
1246 <p>
1247 If true, commands which modify both the working tree and the index
1248 will mark the updated paths with the "assume unchanged" bit in the
1249 index. These marked files are then assumed to stay unchanged in the
1250 working copy, until you mark them otherwise manually - Git will not
1251 detect the file changes by lstat() calls. This is useful on systems
1252 where those are very slow, such as Microsoft Windows.
1254 False by default.
1255 </p>
1256 </dd>
1258 core.preferSymlinkRefs
1259 </dt>
1260 <dd>
1261 <p>
1262 Instead of the default "symref" format for HEAD
1263 and other symbolic reference files, use symbolic links.
1264 This is sometimes needed to work with old scripts that
1265 expect HEAD to be a symbolic link.
1266 </p>
1267 </dd>
1269 core.bare
1270 </dt>
1271 <dd>
1272 <p>
1274 working directory associated with it. If this is the case a
1275 number of commands that require a working directory will be
1276 disabled, such as <a href="git-add.html">git-add(1)</a> or <a href="git-merge.html">git-merge(1)</a>.
1277 </p>
1278 <div class="paragraph"><p>This setting is automatically guessed by <a href="git-clone.html">git-clone(1)</a> or
1280 repository that ends in "/.git" is assumed to be not bare (bare =
1281 false), while all other repositories are assumed to be bare (bare
1282 = true).</p></div>
1283 </dd>
1285 core.worktree
1286 </dt>
1287 <dd>
1288 <p>
1289 Set the path to the root of the working tree.
1290 This can be overridden by the GIT_WORK_TREE environment
1292 The value can an absolute path or relative to the path to
1293 the .git directory, which is either specified by --git-dir
1294 or GIT_DIR, or automatically discovered.
1295 If --git-dir or GIT_DIR is specified but none of
1296 --work-tree, GIT_WORK_TREE and core.worktree is specified,
1297 the current working directory is regarded as the top level
1298 of your working tree.
1299 </p>
1301 file in a ".git" subdirectory of a directory and its value differs
1302 from the latter directory (e.g. "/path/to/.git/config" has
1303 core.worktree set to "/different/path"), which is most likely a
1304 misconfiguration. Running git commands in the "/path/to" directory will
1305 still use "/different/path" as the root of the work tree and can cause
1306 confusion unless you know what you are doing (e.g. you are creating a
1307 read-only snapshot of the same index to a location different from the
1309 </dd>
1311 core.logAllRefUpdates
1312 </dt>
1313 <dd>
1314 <p>
1316 "$GIT_DIR/logs/<ref>", by appending the new and old
1317 SHA1, the date/time and the reason of the update, but
1318 only when the file exists. If this configuration
1319 variable is set to true, missing "$GIT_DIR/logs/<ref>"
1320 file is automatically created for branch heads.
1321 </p>
1325 a working directory associated with it, and false by
1326 default in a bare repository.</p></div>
1327 </dd>
1329 core.repositoryFormatVersion
1330 </dt>
1331 <dd>
1332 <p>
1333 Internal variable identifying the repository format and layout
1334 version.
1335 </p>
1336 </dd>
1338 core.sharedRepository
1339 </dt>
1340 <dd>
1341 <p>
1343 several users in a group (making sure all the files and objects are
1345 repository will be readable by all users, additionally to being
1349 user’s umask value (whereas the other options will only override
1351 the repo read/write-able for the owner and group, but inaccessible to
1353 repository that is group-readable but not group-writable.
1355 </p>
1356 </dd>
1358 core.warnAmbiguousRefs
1359 </dt>
1360 <dd>
1361 <p>
1362 If true, git will warn you if the ref name you passed it is ambiguous
1363 and might match multiple refs in the .git/refs/ tree. True by default.
1364 </p>
1365 </dd>
1367 core.compression
1368 </dt>
1369 <dd>
1370 <p>
1374 If set, this provides a default to other compression variables,
1376 </p>
1377 </dd>
1379 core.loosecompression
1380 </dt>
1381 <dd>
1382 <p>
1386 slowest. If not set, defaults to core.compression. If that is
1387 not set, defaults to 1 (best speed).
1388 </p>
1389 </dd>
1391 core.packedGitWindowSize
1392 </dt>
1393 <dd>
1394 <p>
1395 Number of bytes of a pack file to map into memory in a
1396 single mapping operation. Larger window sizes may allow
1397 your system to process a smaller number of large pack files
1398 more quickly. Smaller window sizes will negatively affect
1399 performance due to increased calls to the operating system’s
1400 memory manager, but may improve performance when accessing
1401 a large number of large pack files.
1402 </p>
1405 be reasonable for all users/operating systems. You probably do
1406 not need to adjust this value.</p></div>
1407 <div class="paragraph"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1408 </dd>
1410 core.packedGitLimit
1411 </dt>
1412 <dd>
1413 <p>
1414 Maximum number of bytes to map simultaneously into memory
1415 from pack files. If Git needs to access more than this many
1416 bytes at once to complete an operation it will unmap existing
1417 regions to reclaim virtual address space within the process.
1418 </p>
1419 <div class="paragraph"><p>Default is 256 MiB on 32 bit platforms and 8 GiB on 64 bit platforms.
1420 This should be reasonable for all users/operating systems, except on
1421 the largest projects. You probably do not need to adjust this value.</p></div>
1422 <div class="paragraph"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1423 </dd>
1425 core.deltaBaseCacheLimit
1426 </dt>
1427 <dd>
1428 <p>
1429 Maximum number of bytes to reserve for caching base objects
1430 that may be referenced by multiple deltified objects. By storing the
1431 entire decompressed base objects in a cache Git is able
1432 to avoid unpacking and decompressing frequently used base
1433 objects multiple times.
1434 </p>
1436 for all users/operating systems, except on the largest projects.
1437 You probably do not need to adjust this value.</p></div>
1438 <div class="paragraph"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1439 </dd>
1441 core.bigFileThreshold
1442 </dt>
1443 <dd>
1444 <p>
1445 Files larger than this size are stored deflated, without
1446 attempting delta compression. Storing large files without
1447 delta compression avoids excessive memory usage, at the
1448 slight expense of increased disk usage.
1449 </p>
1451 for most projects as source code and other text files can still
1453 <div class="paragraph"><p>Common unit suffixes of <em>k</em>, <em>m</em>, or <em>g</em> are supported.</p></div>
1454 <div class="paragraph"><p>Currently only <a href="git-fast-import.html">git-fast-import(1)</a> honors this setting.</p></div>
1455 </dd>
1457 core.excludesfile
1458 </dt>
1459 <dd>
1460 <p>
1463 of files which are not meant to be tracked. "~/" is expanded
1466 </p>
1467 </dd>
1469 core.askpass
1470 </dt>
1471 <dd>
1472 <p>
1473 Some commands (e.g. svn and http interfaces) that interactively
1474 ask for a password can be told to use an external program given
1476 environment variable. If not set, fall back to the value of the
1478 prompt. The external program shall be given a suitable prompt as
1479 command line argument and write the password on its STDOUT.
1480 </p>
1481 </dd>
1483 core.attributesfile
1484 </dt>
1485 <dd>
1486 <p>
1491 </p>
1492 </dd>
1494 core.editor
1495 </dt>
1496 <dd>
1497 <p>
1499 messages by launching an editor uses the value of this
1500 variable when it is set, and the environment variable
1502 </p>
1503 </dd>
1505 core.pager
1506 </dt>
1507 <dd>
1508 <p>
1509 The command that git will use to paginate output. Can
1513 pager. One can change these settings by setting the
1515 these settings can be overridden on a project or
1518 environment variable behaviour above, so if you want
1519 to override git’s default settings this way, you need
1520 to be explicit. For example, to disable the S option
1523 shell by git, which will translate the final command to
1525 </p>
1526 </dd>
1528 core.whitespace
1529 </dt>
1530 <dd>
1531 <p>
1532 A comma separated list of common whitespace problems to
1537 </p>
1539 <li>
1540 <p>
1542 as an error (enabled by default).
1543 </p>
1544 </li>
1545 <li>
1546 <p>
1548 before a tab character in the initial indent part of the line as an
1549 error (enabled by default).
1550 </p>
1551 </li>
1552 <li>
1553 <p>
1555 space characters as an error (not enabled by default).
1556 </p>
1557 </li>
1558 <li>
1559 <p>
1561 the line as an error (not enabled by default).
1562 </p>
1563 </li>
1564 <li>
1565 <p>
1567 (enabled by default).
1568 </p>
1569 </li>
1570 <li>
1571 <p>
1574 </p>
1575 </li>
1576 <li>
1577 <p>
1580 does not trigger if the character before such a carriage-return
1581 is not a whitespace (not enabled by default).
1582 </p>
1583 </li>
1584 <li>
1585 <p>
1589 </p>
1590 </li>
1591 </ul></div>
1592 </dd>
1594 core.fsyncobjectfiles
1595 </dt>
1596 <dd>
1597 <p>
1599 </p>
1601 data writes properly, but can be useful for filesystems that do not use
1602 journalling (traditional UNIX filesystems) or that only journal metadata
1604 </dd>
1606 core.preloadindex
1607 </dt>
1608 <dd>
1609 <p>
1611 </p>
1612 <div class="paragraph"><p>This can speed up operations like <em>git diff</em> and <em>git status</em> especially
1613 on filesystems like NFS that have weak caching semantics and thus
1615 index comparison to the filesystem data in parallel, allowing
1617 </dd>
1619 core.createObject
1620 </dt>
1621 <dd>
1622 <p>
1624 a delete of the source are used to make sure that object creation
1625 will not overwrite existing objects.
1626 </p>
1627 <div class="paragraph"><p>On some file system/operating system combinations, this is unreliable.
1629 check that makes sure that existing object files will not get overwritten.</p></div>
1630 </dd>
1632 core.notesRef
1633 </dt>
1634 <dd>
1635 <p>
1636 When showing commit messages, also show notes which are stored in
1637 the given ref. The ref must be fully qualified. If the given
1638 ref does not exist, it is not an error but means that no
1639 notes should be printed.
1640 </p>
1641 <div class="paragraph"><p>This setting defaults to "refs/notes/commits", and it can be overridden by
1642 the <em>GIT_NOTES_REF</em> environment variable. See <a href="git-notes.html">git-notes(1)</a>.</p></div>
1643 </dd>
1645 core.sparseCheckout
1646 </dt>
1647 <dd>
1648 <p>
1651 </p>
1652 </dd>
1654 add.ignore-errors
1655 </dt>
1657 add.ignoreErrors
1658 </dt>
1659 <dd>
1660 <p>
1665 convention for configuration variables. Newer versions of git
1667 </p>
1668 </dd>
1670 alias.*
1671 </dt>
1672 <dd>
1673 <p>
1675 after defining "alias.last = cat-file commit HEAD", the invocation
1677 confusion and troubles with script usage, aliases that
1678 hide existing git commands are ignored. Arguments are split by
1679 spaces, the usual shell quoting and escaping is supported.
1680 quote pair and a backslash can be used to quote them.
1681 </p>
1683 it will be treated as a shell command. For example, defining
1684 "alias.new = !gitk --all --not ORIG_HEAD", the invocation
1685 "git new" is equivalent to running the shell command
1686 "gitk --all --not ORIG_HEAD". Note that shell commands will be
1687 executed from the top-level directory of a repository, which may
1688 not necessarily be the current directory.</p></div>
1689 </dd>
1691 am.keepcr
1692 </dt>
1693 <dd>
1694 <p>
1695 If true, git-am will call git-mailsplit for patches in mbox format
1700 </p>
1701 </dd>
1703 apply.ignorewhitespace
1704 </dt>
1705 <dd>
1706 <p>
1709 option.
1711 respect all whitespace differences.
1713 </p>
1714 </dd>
1716 apply.whitespace
1717 </dt>
1718 <dd>
1719 <p>
1722 </p>
1723 </dd>
1725 branch.autosetupmerge
1726 </dt>
1727 <dd>
1728 <p>
1731 starting point branch. Note that even if this option is not set,
1735 starting point is a remote-tracking branch; <tt>always</tt> —  automatic setup is done when the starting point is either a
1736 local branch or remote-tracking
1737 branch. This option defaults to true.
1738 </p>
1739 </dd>
1741 branch.autosetuprebase
1742 </dt>
1743 <dd>
1744 <p>
1746 that tracks another branch, this variable tells git to set
1747 up pull to rebase instead of merge (see "branch.<name>.rebase").
1750 other local branches.
1752 remote-tracking branches.
1754 branches.
1755 See "branch.autosetupmerge" for details on how to set up a
1756 branch to track another branch.
1757 This option defaults to never.
1758 </p>
1759 </dd>
1762 </dt>
1763 <dd>
1764 <p>
1768 </p>
1769 </dd>
1772 </dt>
1773 <dd>
1774 <p>
1779 refspec to be marked for merging in FETCH_HEAD. The value is
1780 handled like the remote part of a refspec, and must match a
1781 ref which is fetched from the remote given by
1782 "branch.<name>.remote".
1786 Specify multiple values to get an octopus merge.
1788 another branch in the local repository, you can point
1791 </p>
1792 </dd>
1795 </dt>
1796 <dd>
1797 <p>
1800 option values containing whitespace characters are currently not
1801 supported.
1802 </p>
1803 </dd>
1806 </dt>
1807 <dd>
1808 <p>
1810 instead of merging the default branch from the default remote when
1811 "git pull" is run.
1814 for details).
1815 </p>
1816 </dd>
1819 </dt>
1820 <dd>
1821 <p>
1822 Specify the command to invoke the specified browser. The
1823 specified command is evaluated in shell with the URLs passed
1825 </p>
1826 </dd>
1829 </dt>
1830 <dd>
1831 <p>
1832 Override the path for the given tool that may be used to
1835 </p>
1836 </dd>
1838 clean.requireForce
1839 </dt>
1840 <dd>
1841 <p>
1842 A boolean to make git-clean do nothing unless given -f
1843 or -n. Defaults to true.
1844 </p>
1845 </dd>
1847 color.branch
1848 </dt>
1849 <dd>
1850 <p>
1851 A boolean to enable/disable color in the output of
1853 <tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt> (or <tt>true</tt>), in which case colors are used
1854 only when the output is to a terminal. Defaults to false.
1855 </p>
1856 </dd>
1859 </dt>
1860 <dd>
1861 <p>
1865 refs).
1866 </p>
1867 <div class="paragraph"><p>The value for these configuration variables is a list of colors (at most
1868 two) and attributes (at most one), separated by spaces. The colors
1869 accepted are <tt>normal</tt>, <tt>black</tt>, <tt>red</tt>, <tt>green</tt>, <tt>yellow</tt>, <tt>blue</tt>,
1870 <tt>magenta</tt>, <tt>cyan</tt> and <tt>white</tt>; the attributes are <tt>bold</tt>, <tt>dim</tt>, <tt>ul</tt>,
1872 second is the background. The position of the attribute, if any,
1874 </dd>
1876 color.diff
1877 </dt>
1878 <dd>
1879 <p>
1882 colors only when the output is to the terminal. Defaults to false.
1883 </p>
1884 </dd>
1887 </dt>
1888 <dd>
1889 <p>
1891 which part of the patch to use the specified color, and is one
1895 (highlighting whitespace errors). The values of these variables may be
1897 </p>
1898 </dd>
1901 </dt>
1902 <dd>
1903 <p>
1905 of <tt>branch</tt>, <tt>remoteBranch</tt>, <tt>tag</tt>, <tt>stash</tt> or <tt>HEAD</tt> for local
1906 branches, remote-tracking branches, tags, stash and HEAD, respectively.
1907 </p>
1908 </dd>
1910 color.grep
1911 </dt>
1912 <dd>
1913 <p>
1917 </p>
1918 </dd>
1921 </dt>
1922 <dd>
1923 <p>
1925 part of the line to use the specified color, and is one of
1926 </p>
1930 </dt>
1931 <dd>
1932 <p>
1934 </p>
1935 </dd>
1938 </dt>
1939 <dd>
1940 <p>
1942 </p>
1943 </dd>
1946 </dt>
1947 <dd>
1948 <p>
1950 </p>
1951 </dd>
1954 </dt>
1955 <dd>
1956 <p>
1958 </p>
1959 </dd>
1962 </dt>
1963 <dd>
1964 <p>
1965 matching text
1966 </p>
1967 </dd>
1970 </dt>
1971 <dd>
1972 <p>
1973 non-matching text in selected lines
1974 </p>
1975 </dd>
1978 </dt>
1979 <dd>
1980 <p>
1983 </p>
1984 </dd>
1985 </dl></div>
1986 <div class="paragraph"><p>The values of these variables may be specified as in color.branch.<slot>.</p></div>
1987 </dd>
1989 color.interactive
1990 </dt>
1991 <dd>
1992 <p>
1994 and displays (such as those used by "git-add --interactive").
1996 colors only when the output is to the terminal. Defaults to false.
1997 </p>
1998 </dd>
2001 </dt>
2002 <dd>
2003 <p>
2005 output. <tt><slot></tt> may be <tt>prompt</tt>, <tt>header</tt>, <tt>help</tt> or <tt>error</tt>, for
2006 four distinct types of normal output from interactive
2007 commands. The values of these variables may be specified as
2009 </p>
2010 </dd>
2012 color.pager
2013 </dt>
2014 <dd>
2015 <p>
2016 A boolean to enable/disable colored output when the pager is in
2017 use (default is true).
2018 </p>
2019 </dd>
2021 color.showbranch
2022 </dt>
2023 <dd>
2024 <p>
2025 A boolean to enable/disable color in the output of
2027 <tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt> (or <tt>true</tt>), in which case colors are used
2028 only when the output is to a terminal. Defaults to false.
2029 </p>
2030 </dd>
2032 color.status
2033 </dt>
2034 <dd>
2035 <p>
2036 A boolean to enable/disable color in the output of
2038 <tt>false</tt> (or <tt>never</tt>) or <tt>auto</tt> (or <tt>true</tt>), in which case colors are used
2039 only when the output is to a terminal. Defaults to false.
2040 </p>
2041 </dd>
2044 </dt>
2045 <dd>
2046 <p>
2054 to red). The values of these variables may be specified as in
2056 </p>
2057 </dd>
2059 color.ui
2060 </dt>
2061 <dd>
2062 <p>
2066 terminal. When more specific variables of color.* are set, they always
2067 take precedence over this setting. Defaults to false.
2068 </p>
2069 </dd>
2071 commit.status
2072 </dt>
2073 <dd>
2074 <p>
2075 A boolean to enable/disable inclusion of status information in the
2076 commit message template when using an editor to prepare the commit
2077 message. Defaults to true.
2078 </p>
2079 </dd>
2081 commit.template
2082 </dt>
2083 <dd>
2084 <p>
2085 Specify a file to use as the template for new commit messages.
2087 specified user’s home directory.
2088 </p>
2089 </dd>
2091 diff.autorefreshindex
2092 </dt>
2093 <dd>
2094 <p>
2096 files, do not consider stat-only change as changed.
2098 update the cached stat information for paths whose
2099 contents in the work tree match the contents in the
2100 index. This option defaults to true. Note that this
2103 </p>
2104 </dd>
2106 diff.external
2107 </dt>
2108 <dd>
2109 <p>
2110 If this config variable is set, diff generation is not
2111 performed using the internal diff machinery, but using the
2113 environment variable. The command is called with parameters
2115 you want to use an external diff program only on a subset of
2117 </p>
2118 </dd>
2120 diff.mnemonicprefix
2121 </dt>
2122 <dd>
2123 <p>
2126 this configuration is in effect, reverse diff output also swaps
2127 the order of the prefixes:
2128 </p>
2132 </dt>
2133 <dd>
2134 <p>
2135 compares the (i)ndex and the (w)ork tree;
2136 </p>
2137 </dd>
2140 </dt>
2141 <dd>
2142 <p>
2143 compares a (c)ommit and the (w)ork tree;
2144 </p>
2145 </dd>
2148 </dt>
2149 <dd>
2150 <p>
2151 compares a (c)ommit and the (i)ndex;
2152 </p>
2153 </dd>
2156 </dt>
2157 <dd>
2158 <p>
2159 compares an (o)bject and a (w)ork tree entity;
2160 </p>
2161 </dd>
2164 </dt>
2165 <dd>
2166 <p>
2168 </p>
2169 </dd>
2170 </dl></div>
2171 </dd>
2173 diff.noprefix
2174 </dt>
2175 <dd>
2176 <p>
2178 </p>
2179 </dd>
2181 diff.renameLimit
2182 </dt>
2183 <dd>
2184 <p>
2185 The number of files to consider when performing the copy/rename
2187 </p>
2188 </dd>
2190 diff.renames
2191 </dt>
2192 <dd>
2193 <p>
2194 Tells git to detect renames. If set to any boolean value, it
2195 will enable basic rename detection. If set to "copies" or
2196 "copy", it will detect copies, as well.
2197 </p>
2198 </dd>
2200 diff.ignoreSubmodules
2201 </dt>
2202 <dd>
2203 <p>
2204 Sets the default value of --ignore-submodules. Note that this
2207 this setting when reporting uncommitted changes.
2208 </p>
2209 </dd>
2211 diff.suppressBlankEmpty
2212 </dt>
2213 <dd>
2214 <p>
2215 A boolean to inhibit the standard behavior of printing a space
2216 before each empty output line. Defaults to false.
2217 </p>
2218 </dd>
2220 diff.tool
2221 </dt>
2222 <dd>
2223 <p>
2227 and plus "kompare".
2228 </p>
2229 </dd>
2232 </dt>
2233 <dd>
2234 <p>
2235 Override the path for the given tool. This is useful in case
2236 your tool is not in the PATH.
2237 </p>
2238 </dd>
2241 </dt>
2242 <dd>
2243 <p>
2244 Specify the command to invoke the specified diff tool.
2245 The specified command is evaluated in shell with the following
2248 is set to the name of the temporary file containing the contents
2249 of the diff post-image.
2250 </p>
2251 </dd>
2253 difftool.prompt
2254 </dt>
2255 <dd>
2256 <p>
2257 Prompt before each invocation of the diff tool.
2258 </p>
2259 </dd>
2261 diff.wordRegex
2262 </dt>
2263 <dd>
2264 <p>
2265 A POSIX Extended Regular Expression used to determine what is a "word"
2266 when performing word-by-word difference calculations. Character
2267 sequences that match the regular expression are "words", all other
2269 </p>
2270 </dd>
2272 fetch.recurseSubmodules
2273 </dt>
2274 <dd>
2275 <p>
2276 A boolean value which changes the behavior for fetch and pull, the
2277 default is to not recursively fetch populated submodules unless
2278 configured otherwise.
2279 </p>
2280 </dd>
2282 fetch.unpackLimit
2283 </dt>
2284 <dd>
2285 <p>
2286 If the number of objects fetched over the git native
2287 transfer is below this
2288 limit, then the objects will be unpacked into loose object
2289 files. However if the number of received objects equals or
2290 exceeds this limit then the received pack will be stored as
2291 a pack, after adding any missing delta bases. Storing the
2292 pack from a push can make the push operation complete faster,
2293 especially on slow filesystems. If not set, the value of
2295 </p>
2296 </dd>
2298 format.attach
2299 </dt>
2300 <dd>
2301 <p>
2302 Enable multipart/mixed attachments as the default for
2304 which will enable attachments as the default and set the
2305 value as the boundary. See the --attach option in
2307 </p>
2308 </dd>
2310 format.numbered
2311 </dt>
2312 <dd>
2313 <p>
2314 A boolean which can enable or disable sequence numbers in patch
2315 subjects. It defaults to "auto" which enables it only if there
2316 is more than one patch. It can be enabled or disabled for all
2319 </p>
2320 </dd>
2322 format.headers
2323 </dt>
2324 <dd>
2325 <p>
2326 Additional email headers to include in a patch to be submitted
2328 </p>
2329 </dd>
2331 format.to
2332 </dt>
2334 format.cc
2335 </dt>
2336 <dd>
2337 <p>
2338 Additional recipients to include in a patch to be submitted
2339 by mail. See the --to and --cc options in
2341 </p>
2342 </dd>
2344 format.subjectprefix
2345 </dt>
2346 <dd>
2347 <p>
2349 subject prefix. Use this variable to change that prefix.
2350 </p>
2351 </dd>
2353 format.signature
2354 </dt>
2355 <dd>
2356 <p>
2357 The default for format-patch is to output a signature containing
2358 the git version number. Use this variable to change that default.
2359 Set this variable to the empty string ("") to suppress
2360 signature generation.
2361 </p>
2362 </dd>
2364 format.suffix
2365 </dt>
2366 <dd>
2367 <p>
2368 The default for format-patch is to output files with the suffix
2370 include the dot if you want it).
2371 </p>
2372 </dd>
2374 format.pretty
2375 </dt>
2376 <dd>
2377 <p>
2378 The default pretty format for log/show/whatchanged command,
2381 </p>
2382 </dd>
2384 format.thread
2385 </dt>
2386 <dd>
2387 <p>
2390 makes every mail a reply to the head of the series,
2391 where the head is chosen from the cover letter, the
2395 value disables threading.
2396 </p>
2397 </dd>
2399 format.signoff
2400 </dt>
2401 <dd>
2402 <p>
2405 patch should be a conscious act and means that you certify you have
2406 the rights to submit this work under the same open source license.
2408 </p>
2409 </dd>
2411 gc.aggressiveWindow
2412 </dt>
2413 <dd>
2414 <p>
2415 The window size parameter used in the delta compression
2417 to 250.
2418 </p>
2419 </dd>
2421 gc.auto
2422 </dt>
2423 <dd>
2424 <p>
2425 When there are approximately more than this many loose
2427 Some Porcelain commands use this command to perform a
2428 light-weight garbage collection from time to time. The
2430 </p>
2431 </dd>
2433 gc.autopacklimit
2434 </dt>
2435 <dd>
2436 <p>
2437 When there are more than this many packs that are not
2439 --auto</tt> consolidates them into one larger pack. The
2441 </p>
2442 </dd>
2444 gc.packrefs
2445 </dt>
2446 <dd>
2447 <p>
2449 unclonable by Git versions prior to 1.5.1.2 over dumb
2450 transports such as HTTP. This variable determines whether
2452 to enable it within all non-bare repos or it can be set to a
2454 </p>
2455 </dd>
2457 gc.pruneexpire
2458 </dt>
2459 <dd>
2460 <p>
2462 Override the grace period with this config variable. The value
2463 "now" may be used to disable this grace period and always prune
2464 unreachable objects immediately.
2465 </p>
2466 </dd>
2468 gc.reflogexpire
2469 </dt>
2472 </dt>
2473 <dd>
2474 <p>
2477 "refs/stash") in the middle the setting applies only to
2479 </p>
2480 </dd>
2482 gc.reflogexpireunreachable
2483 </dt>
2486 </dt>
2487 <dd>
2488 <p>
2490 this time and are not reachable from the current tip;
2492 in the middle, the setting applies only to the refs that
2494 </p>
2495 </dd>
2497 gc.rerereresolved
2498 </dt>
2499 <dd>
2500 <p>
2501 Records of conflicted merge you resolved earlier are
2504 </p>
2505 </dd>
2507 gc.rerereunresolved
2508 </dt>
2509 <dd>
2510 <p>
2511 Records of conflicted merge you have not resolved are
2514 </p>
2515 </dd>
2517 gitcvs.commitmsgannotation
2518 </dt>
2519 <dd>
2520 <p>
2521 Append this string to each commit message. Set to empty string
2522 to disable this feature. Defaults to "via git-CVS emulator".
2523 </p>
2524 </dd>
2526 gitcvs.enabled
2527 </dt>
2528 <dd>
2529 <p>
2530 Whether the CVS server interface is enabled for this repository.
2532 </p>
2533 </dd>
2535 gitcvs.logfile
2536 </dt>
2537 <dd>
2538 <p>
2539 Path to a log file where the CVS server interface well… logs
2541 </p>
2542 </dd>
2544 gitcvs.usecrlfattr
2545 </dt>
2546 <dd>
2547 <p>
2548 If true, the server will look up the end-of-line conversion
2550 the attributes force git to treat a file as text,
2552 treat it as text. If they suppress text conversion, the file
2554 the client might otherwise do. If the attributes do not allow
2557 </p>
2558 </dd>
2560 gitcvs.allbinary
2561 </dt>
2562 <dd>
2563 <p>
2566 unresolved files are sent to the client in
2568 as binary files, which suppresses any newline munging it
2569 otherwise might do. Alternatively, if it is set to "guess",
2570 then the contents of the file are examined to decide if
2572 </p>
2573 </dd>
2575 gitcvs.dbname
2576 </dt>
2577 <dd>
2578 <p>
2579 Database used by git-cvsserver to cache revision information
2580 derived from the git repository. The exact meaning depends on the
2581 used database driver, for SQLite (which is the default driver) this
2582 is a filename. Supports variable substitution (see
2583 <a href="git-cvsserver.html">git-cvsserver(1)</a> for details). May not contain semicolons (<tt>;</tt>).
2585 </p>
2586 </dd>
2588 gitcvs.dbdriver
2589 </dt>
2590 <dd>
2591 <p>
2592 Used Perl DBI driver. You can specify any available driver
2593 for this here, but it might not work. git-cvsserver is tested
2598 </p>
2599 </dd>
2601 gitcvs.dbuser, gitcvs.dbpass
2602 </dt>
2603 <dd>
2604 <p>
2606 since SQLite has no concept of database users and/or passwords.
2609 </p>
2610 </dd>
2612 gitcvs.dbTableNamePrefix
2613 </dt>
2614 <dd>
2615 <p>
2616 Database table name prefix. Prepended to the names of any
2617 database tables used, allowing a single database to be used
2618 for several repositories. Supports variable substitution (see
2620 characters will be replaced with underscores.
2621 </p>
2622 </dd>
2623 </dl></div>
2628 access method.</p></div>
2631 gui.commitmsgwidth
2632 </dt>
2633 <dd>
2634 <p>
2635 Defines how wide the commit message window is in the
2637 </p>
2638 </dd>
2640 gui.diffcontext
2641 </dt>
2642 <dd>
2643 <p>
2644 Specifies how many context lines should be used in calls to diff
2646 </p>
2647 </dd>
2649 gui.encoding
2650 </dt>
2651 <dd>
2652 <p>
2653 Specifies the default encoding to use for displaying of
2657 If this option is not set, the tools default to the
2658 locale encoding.
2659 </p>
2660 </dd>
2662 gui.matchtrackingbranch
2663 </dt>
2664 <dd>
2665 <p>
2667 default to tracking remote branches with matching names or
2668 not. Default: "false".
2669 </p>
2670 </dd>
2672 gui.newbranchtemplate
2673 </dt>
2674 <dd>
2675 <p>
2676 Is used as suggested name when creating new branches using the
2678 </p>
2679 </dd>
2681 gui.pruneduringfetch
2682 </dt>
2683 <dd>
2684 <p>
2686 performing a fetch. The default value is "false".
2687 </p>
2688 </dd>
2690 gui.trustmtime
2691 </dt>
2692 <dd>
2693 <p>
2695 timestamp or not. By default the timestamps are not trusted.
2696 </p>
2697 </dd>
2699 gui.spellingdictionary
2700 </dt>
2701 <dd>
2702 <p>
2703 Specifies the dictionary used for spell checking commit messages in
2705 off.
2706 </p>
2707 </dd>
2709 gui.fastcopyblame
2710 </dt>
2711 <dd>
2712 <p>
2714 location detection. It makes blame significantly faster on huge
2715 repositories at the expense of less thorough copy detection.
2716 </p>
2717 </dd>
2719 gui.copyblamethreshold
2720 </dt>
2721 <dd>
2722 <p>
2724 detection, measured in alphanumeric characters. See the
2726 </p>
2727 </dd>
2729 gui.blamehistoryctx
2730 </dt>
2731 <dd>
2732 <p>
2733 Specifies the radius of history context in days to show in
2736 variable is set to zero, the whole history is shown.
2737 </p>
2738 </dd>
2741 </dt>
2742 <dd>
2743 <p>
2744 Specifies the shell command line to execute when the corresponding item
2746 mandatory for every tool. The command is executed from the root of
2747 the working directory, and in the environment it receives the name of
2751 </p>
2752 </dd>
2755 </dt>
2756 <dd>
2757 <p>
2758 Run the tool only if a diff is selected in the GUI. It guarantees
2760 </p>
2761 </dd>
2764 </dt>
2765 <dd>
2766 <p>
2767 Run the command silently, without creating a window to display its
2768 output.
2769 </p>
2770 </dd>
2773 </dt>
2774 <dd>
2775 <p>
2776 Don’t rescan the working directory for changes after the tool
2777 finishes execution.
2778 </p>
2779 </dd>
2782 </dt>
2783 <dd>
2784 <p>
2785 Show a confirmation dialog before actually running the tool.
2786 </p>
2787 </dd>
2790 </dt>
2791 <dd>
2792 <p>
2793 Request a string argument from the user, and pass it to the tool
2797 the dialog uses a built-in generic prompt; otherwise the exact
2798 value of the variable is used.
2799 </p>
2800 </dd>
2803 </dt>
2804 <dd>
2805 <p>
2806 Request a single valid revision from the user, and set the
2809 </p>
2810 </dd>
2813 </dt>
2814 <dd>
2815 <p>
2817 This is useful for tools similar to merge or rebase, but not
2818 for things like checkout or reset.
2819 </p>
2820 </dd>
2823 </dt>
2824 <dd>
2825 <p>
2826 Specifies the title to use for the prompt dialog. The default
2827 is the tool name.
2828 </p>
2829 </dd>
2832 </dt>
2833 <dd>
2834 <p>
2835 Specifies the general prompt string to display at the top of
2837 The default value includes the actual command.
2838 </p>
2839 </dd>
2841 help.browser
2842 </dt>
2843 <dd>
2844 <p>
2845 Specify the browser that will be used to display help in the
2847 </p>
2848 </dd>
2850 help.format
2851 </dt>
2852 <dd>
2853 <p>
2855 Values <em>man</em>, <em>info</em>, <em>web</em> and <em>html</em> are supported. <em>man</em> is
2857 </p>
2858 </dd>
2860 help.autocorrect
2861 </dt>
2862 <dd>
2863 <p>
2864 Automatically correct and execute mistyped commands after
2865 waiting for the given number of deciseconds (0.1 sec). If more
2866 than one command can be deduced from the entered text, nothing
2867 will be executed. If the value of this option is negative,
2868 the corrected command will be executed immediately. If the
2869 value is 0 - the command will be just shown but not executed.
2870 This is the default.
2871 </p>
2872 </dd>
2874 http.proxy
2875 </dt>
2876 <dd>
2877 <p>
2881 </p>
2882 </dd>
2884 http.sslVerify
2885 </dt>
2886 <dd>
2887 <p>
2888 Whether to verify the SSL certificate when fetching or pushing
2890 variable.
2891 </p>
2892 </dd>
2894 http.sslCert
2895 </dt>
2896 <dd>
2897 <p>
2898 File containing the SSL certificate when fetching or pushing
2900 variable.
2901 </p>
2902 </dd>
2904 http.sslKey
2905 </dt>
2906 <dd>
2907 <p>
2908 File containing the SSL private key when fetching or pushing
2910 variable.
2911 </p>
2912 </dd>
2914 http.sslCertPasswordProtected
2915 </dt>
2916 <dd>
2917 <p>
2918 Enable git’s password prompt for the SSL certificate. Otherwise
2919 OpenSSL will prompt the user, possibly many times, if the
2920 certificate or private key is encrypted. Can be overridden by the
2922 </p>
2923 </dd>
2925 http.sslCAInfo
2926 </dt>
2927 <dd>
2928 <p>
2929 File containing the certificates to verify the peer with when
2930 fetching or pushing over HTTPS. Can be overridden by the
2932 </p>
2933 </dd>
2935 http.sslCAPath
2936 </dt>
2937 <dd>
2938 <p>
2939 Path containing files with the CA certificates to verify the peer
2940 with when fetching or pushing over HTTPS. Can be overridden
2942 </p>
2943 </dd>
2945 http.maxRequests
2946 </dt>
2947 <dd>
2948 <p>
2949 How many HTTP requests to launch in parallel. Can be overridden
2951 </p>
2952 </dd>
2954 http.minSessions
2955 </dt>
2956 <dd>
2957 <p>
2958 The number of curl sessions (counted across slots) to be kept across
2959 requests. They will not be ended with curl_easy_cleanup() until
2960 http_cleanup() is invoked. If USE_CURL_MULTI is not defined, this
2962 </p>
2963 </dd>
2965 http.postBuffer
2966 </dt>
2967 <dd>
2968 <p>
2969 Maximum size in bytes of the buffer used by smart HTTP
2970 transports when POSTing data to the remote system.
2971 For requests larger than this buffer size, HTTP/1.1 and
2972 Transfer-Encoding: chunked is used to avoid creating a
2973 massive pack file locally. Default is 1 MiB, which is
2974 sufficient for most requests.
2975 </p>
2976 </dd>
2978 http.lowSpeedLimit, http.lowSpeedTime
2979 </dt>
2980 <dd>
2981 <p>
2986 </p>
2987 </dd>
2989 http.noEPSV
2990 </dt>
2991 <dd>
2992 <p>
2993 A boolean which disables using of EPSV ftp command by curl.
2996 environment variable. Default is false (curl will use EPSV).
2997 </p>
2998 </dd>
3000 http.useragent
3001 </dt>
3002 <dd>
3003 <p>
3004 The HTTP USER_AGENT string presented to an HTTP server. The default
3005 value represents the version of the client git such as git/1.7.1.
3006 This option allows you to override this value to a more common value
3007 such as Mozilla/4.0. This may be necessary, for instance, if
3008 connecting through a firewall that restricts HTTP connections to a set
3009 of common USER_AGENT strings (but not including those like git/1.7.1).
3011 </p>
3012 </dd>
3014 i18n.commitEncoding
3015 </dt>
3016 <dd>
3017 <p>
3018 Character encoding the commit messages are stored in; git itself
3019 does not care per se, but this information is necessary e.g. when
3020 importing commits from emails or in the gitk graphical history
3021 browser (and possibly at other places in the future or in other
3022 porcelains). See e.g. <a href="git-mailinfo.html">git-mailinfo(1)</a>. Defaults to <em>utf-8</em>.
3023 </p>
3024 </dd>
3026 i18n.logOutputEncoding
3027 </dt>
3028 <dd>
3029 <p>
3030 Character encoding the commit messages are converted to when
3032 </p>
3033 </dd>
3035 imap
3036 </dt>
3037 <dd>
3038 <p>
3041 </p>
3042 </dd>
3044 init.templatedir
3045 </dt>
3046 <dd>
3047 <p>
3048 Specify the directory from which templates will be copied.
3050 </p>
3051 </dd>
3053 instaweb.browser
3054 </dt>
3055 <dd>
3056 <p>
3057 Specify the program that will be used to browse your working
3059 </p>
3060 </dd>
3062 instaweb.httpd
3063 </dt>
3064 <dd>
3065 <p>
3066 The HTTP daemon command-line to start gitweb on your working
3068 </p>
3069 </dd>
3071 instaweb.local
3072 </dt>
3073 <dd>
3074 <p>
3076 be bound to the local IP (127.0.0.1).
3077 </p>
3078 </dd>
3080 instaweb.modulepath
3081 </dt>
3082 <dd>
3083 <p>
3085 instead of /usr/lib/apache2/modules. Only used if httpd
3086 is Apache.
3087 </p>
3088 </dd>
3090 instaweb.port
3091 </dt>
3092 <dd>
3093 <p>
3094 The port number to bind the gitweb httpd to. See
3096 </p>
3097 </dd>
3099 interactive.singlekey
3100 </dt>
3101 <dd>
3102 <p>
3103 In interactive commands, allow the user to provide one-letter
3104 input with a single key (i.e., without hitting enter).
3107 ignored if portable keystroke input is not available.
3108 </p>
3109 </dd>
3111 log.date
3112 </dt>
3113 <dd>
3114 <p>
3118 <tt>default</tt>, <tt>iso</tt>, <tt>rfc</tt>, and <tt>short</tt>; see <a href="git-log.html">git-log(1)</a>
3119 for details.
3120 </p>
3121 </dd>
3123 log.decorate
3124 </dt>
3125 <dd>
3126 <p>
3127 Print out the ref names of any commits that are shown by the log
3130 specified, the full ref name (including prefix) will be printed.
3132 </p>
3133 </dd>
3135 log.showroot
3136 </dt>
3137 <dd>
3138 <p>
3139 If true, the initial commit will be shown as a big creation event.
3140 This is equivalent to a diff against an empty tree.
3141 Tools like <a href="git-log.html">git-log(1)</a> or <a href="git-whatchanged.html">git-whatchanged(1)</a>, which
3142 normally hide the root commit will now show it. True by default.
3143 </p>
3144 </dd>
3146 mailmap.file
3147 </dt>
3148 <dd>
3149 <p>
3150 The location of an augmenting mailmap file. The default
3151 mailmap, located in the root of the repository, is loaded
3152 first, then the mailmap file pointed to by this variable.
3153 The location of the mailmap file may be in a repository
3154 subdirectory, or somewhere outside of the repository itself.
3155 See <a href="git-shortlog.html">git-shortlog(1)</a> and <a href="git-blame.html">git-blame(1)</a>.
3156 </p>
3157 </dd>
3159 man.viewer
3160 </dt>
3161 <dd>
3162 <p>
3163 Specify the programs that may be used to display help in the
3165 </p>
3166 </dd>
3169 </dt>
3170 <dd>
3171 <p>
3172 Specify the command to invoke the specified man viewer. The
3173 specified command is evaluated in shell with the man page
3175 </p>
3176 </dd>
3179 </dt>
3180 <dd>
3181 <p>
3182 Override the path for the given tool that may be used to
3184 </p>
3185 </dd>
3187 merge.conflictstyle
3188 </dt>
3189 <dd>
3190 <p>
3191 Specify the style in which conflicted hunks are written out to
3192 working tree files upon merge. The default is "merge", which
3195 a <tt>>>>>>>></tt> marker. An alternate style, "diff3", adds a <tt>|||||||</tt>
3197 </p>
3198 </dd>
3200 merge.log
3201 </dt>
3202 <dd>
3203 <p>
3204 In addition to branch names, populate the log message with at
3205 most the specified number of one-line descriptions from the
3206 actual commits that are being merged. Defaults to false, and
3207 true is a synonym for 20.
3208 </p>
3209 </dd>
3211 merge.renameLimit
3212 </dt>
3213 <dd>
3214 <p>
3215 The number of files to consider when performing rename detection
3216 during a merge; if not specified, defaults to the value of
3217 diff.renameLimit.
3218 </p>
3219 </dd>
3221 merge.renormalize
3222 </dt>
3223 <dd>
3224 <p>
3225 Tell git that canonical representation of files in the
3226 repository has changed over time (e.g. earlier commits record
3227 text files with CRLF line endings, but recent ones use LF line
3228 endings). In such a repository, git can convert the data
3229 recorded in commits to a canonical form before performing a
3230 merge to reduce unnecessary conflicts. For more information,
3231 see section "Merging branches with differing checkin/checkout
3233 </p>
3234 </dd>
3236 merge.stat
3237 </dt>
3238 <dd>
3239 <p>
3240 Whether to print the diffstat between ORIG_HEAD and the merge result
3241 at the end of the merge. True by default.
3242 </p>
3243 </dd>
3245 merge.tool
3246 </dt>
3247 <dd>
3248 <p>
3249 Controls which merge resolution program is used by
3253 "opendiff". Any other value is treated is custom merge tool
3255 </p>
3256 </dd>
3258 merge.verbosity
3259 </dt>
3260 <dd>
3261 <p>
3262 Controls the amount of output shown by the recursive merge
3263 strategy. Level 0 outputs nothing except a final error
3264 message if conflicts were detected. Level 1 outputs only
3266 above outputs debugging information. The default is level 2.
3268 </p>
3269 </dd>
3272 </dt>
3273 <dd>
3274 <p>
3275 Defines a human-readable name for a custom low-level
3277 </p>
3278 </dd>
3281 </dt>
3282 <dd>
3283 <p>
3284 Defines the command that implements a custom low-level
3286 </p>
3287 </dd>
3290 </dt>
3291 <dd>
3292 <p>
3293 Names a low-level merge driver to be used when
3294 performing an internal merge between common ancestors.
3296 </p>
3297 </dd>
3300 </dt>
3301 <dd>
3302 <p>
3303 Override the path for the given tool. This is useful in case
3304 your tool is not in the PATH.
3305 </p>
3306 </dd>
3309 </dt>
3310 <dd>
3311 <p>
3312 Specify the command to invoke the specified merge tool. The
3313 specified command is evaluated in shell with the following
3315 containing the common base of the files to be merged, if available;
3318 file containing the contents of the file from the branch being
3320 tool should write the results of a successful merge.
3321 </p>
3322 </dd>
3325 </dt>
3326 <dd>
3327 <p>
3328 For a custom merge command, specify whether the exit code of
3329 the merge command can be used to determine whether the merge was
3330 successful. If this is not set to true then the merge target file
3331 timestamp is checked and the merge assumed to have been successful
3332 if the file has been updated, otherwise the user is prompted to
3333 indicate the success of the merge.
3334 </p>
3335 </dd>
3337 mergetool.keepBackup
3338 </dt>
3339 <dd>
3340 <p>
3341 After performing a merge, the original file with conflict markers
3345 </p>
3346 </dd>
3348 mergetool.keepTemporaries
3349 </dt>
3350 <dd>
3351 <p>
3352 When invoking a custom merge tool, git uses a set of temporary
3353 files to pass to the tool. If the tool returns an error and this
3355 preserved, otherwise they will be removed after the tool has
3357 </p>
3358 </dd>
3360 mergetool.prompt
3361 </dt>
3362 <dd>
3363 <p>
3364 Prompt before each invocation of the merge resolution program.
3365 </p>
3366 </dd>
3368 notes.displayRef
3369 </dt>
3370 <dd>
3371 <p>
3372 The (fully qualified) refname from which to show notes when
3373 showing commit messages. The value of this variable can be set
3374 to a glob, in which case notes from all matching refs will be
3375 shown. You may also specify this configuration variable
3376 several times. A warning will be issued for refs that do not
3377 exist, but a glob that does not match any refs is silently
3378 ignored.
3379 </p>
3380 <div class="paragraph"><p>This setting can be overridden with the <tt>GIT_NOTES_DISPLAY_REF</tt>
3381 environment variable, which must be a colon separated list of refs or
3382 globs.</p></div>
3384 GIT_NOTES_REF) is also implicitly added to the list of refs to be
3385 displayed.</p></div>
3386 </dd>
3389 </dt>
3390 <dd>
3391 <p>
3394 automatically copies your notes from the original to the
3396 "notes.rewriteRef" below.
3397 </p>
3398 </dd>
3400 notes.rewriteMode
3401 </dt>
3402 <dd>
3403 <p>
3404 When copying notes during a rewrite (see the
3405 "notes.rewrite.<command>" option), determines what to do if
3406 the target commit already has a note. Must be one of
3409 </p>
3410 <div class="paragraph"><p>This setting can be overridden with the <tt>GIT_NOTES_REWRITE_MODE</tt>
3411 environment variable.</p></div>
3412 </dd>
3414 notes.rewriteRef
3415 </dt>
3416 <dd>
3417 <p>
3418 When copying notes during a rewrite, specifies the (fully
3419 qualified) ref whose notes should be copied. The ref may be a
3420 glob, in which case notes in all matching refs will be copied.
3421 You may also specify this configuration several times.
3422 </p>
3424 enable note rewriting.</p></div>
3425 <div class="paragraph"><p>This setting can be overridden with the <tt>GIT_NOTES_REWRITE_REF</tt>
3426 environment variable, which must be a colon separated list of refs or
3427 globs.</p></div>
3428 </dd>
3430 pack.window
3431 </dt>
3432 <dd>
3433 <p>
3435 window size is given on the command line. Defaults to 10.
3436 </p>
3437 </dd>
3439 pack.depth
3440 </dt>
3441 <dd>
3442 <p>
3443 The maximum delta depth used by <a href="git-pack-objects.html">git-pack-objects(1)</a> when no
3444 maximum depth is given on the command line. Defaults to 50.
3445 </p>
3446 </dd>
3448 pack.windowMemory
3449 </dt>
3450 <dd>
3451 <p>
3453 when no limit is given on the command line. The value can be
3455 limit.
3456 </p>
3457 </dd>
3459 pack.compression
3460 </dt>
3461 <dd>
3462 <p>
3466 slowest. If not set, defaults to core.compression. If that is
3468 compromise between speed and compression (currently equivalent
3469 to level 6)."
3470 </p>
3471 <div class="paragraph"><p>Note that changing the compression level will not automatically recompress
3472 all existing objects. You can force recompression by passing the -F option
3474 </dd>
3476 pack.deltaCacheSize
3477 </dt>
3478 <dd>
3479 <p>
3480 The maximum memory in bytes used for caching deltas in
3482 This cache is used to speed up the writing object phase by not
3483 having to recompute the final delta result once the best match
3484 for all objects is found. Repacking large repositories on machines
3485 which are tight with memory might be badly impacted by this though,
3486 especially if this cache pushes the system into swapping.
3488 used to virtually disable this cache. Defaults to 256 MiB.
3489 </p>
3490 </dd>
3492 pack.deltaCacheLimit
3493 </dt>
3494 <dd>
3495 <p>
3496 The maximum size of a delta, that is cached in
3498 writing object phase by not having to recompute the final delta
3499 result once the best match for all objects is found. Defaults to 1000.
3500 </p>
3501 </dd>
3503 pack.threads
3504 </dt>
3505 <dd>
3506 <p>
3507 Specifies the number of threads to spawn when searching for best
3509 be compiled with pthreads otherwise this option is ignored with a
3510 warning. This is meant to reduce packing time on multiprocessor
3511 machines. The required amount of memory for the delta search window
3512 is however multiplied by the number of threads.
3514 and set the number of threads accordingly.
3515 </p>
3516 </dd>
3518 pack.indexVersion
3519 </dt>
3520 <dd>
3521 <p>
3522 Specify the default pack index version. Valid values are 1 for
3524 the new pack index with capabilities for packs larger than 4 GB
3525 as well as proper protection against the repacking of corrupted
3527 and this config option ignored whenever the corresponding pack is
3528 larger than 2 GB.
3529 </p>
3530 <div class="paragraph"><p>If you have an old git that does not understand the version 2 <tt>*.idx</tt> file,
3532 that will copy both <tt>*.pack</tt> file and corresponding <tt>*.idx</tt> file from the
3533 other side may give you a repository that cannot be accessed with your
3535 you can use <a href="git-index-pack.html">git-index-pack(1)</a> on the *.pack file to regenerate
3537 </dd>
3539 pack.packSizeLimit
3540 </dt>
3541 <dd>
3542 <p>
3543 The maximum size of a pack. This setting only affects
3544 packing to a file when repacking, i.e. the git:// protocol
3547 limited to 1 MiB. The default is unlimited.
3549 supported.
3550 </p>
3551 </dd>
3554 </dt>
3555 <dd>
3556 <p>
3557 If the value is boolean, turns on or off pagination of the
3558 output of a particular git subcommand when writing to a tty.
3559 Otherwise, turns on pagination for the subcommand using the
3562 precedence over this option. To disable pagination for all
3564 </p>
3565 </dd>
3568 </dt>
3569 <dd>
3570 <p>
3571 Alias for a --pretty= format string, as specified in
3573 as the built-in pretty formats could. For example,
3577 Note that an alias with the same name as a built-in format
3578 will be silently ignored.
3579 </p>
3580 </dd>
3582 pull.octopus
3583 </dt>
3584 <dd>
3585 <p>
3586 The default merge strategy to use when pulling multiple branches
3587 at once.
3588 </p>
3589 </dd>
3591 pull.twohead
3592 </dt>
3593 <dd>
3594 <p>
3595 The default merge strategy to use when pulling a single branch.
3596 </p>
3597 </dd>
3599 push.default
3600 </dt>
3601 <dd>
3602 <p>
3603 Defines the action git push should take if no refspec is given
3604 on the command line, no refspec is configured in the remote, and
3605 no refspec is implied by any of the options given on the command
3606 line. Possible values are:
3607 </p>
3609 <li>
3610 <p>
3612 </p>
3613 </li>
3614 <li>
3615 <p>
3617 All branches having the same name in both ends are considered to be
3618 matching. This is the default.
3619 </p>
3620 </li>
3621 <li>
3622 <p>
3624 </p>
3625 </li>
3626 <li>
3627 <p>
3629 </p>
3630 </li>
3631 <li>
3632 <p>
3634 </p>
3635 </li>
3636 </ul></div>
3637 </dd>
3639 rebase.stat
3640 </dt>
3641 <dd>
3642 <p>
3643 Whether to show a diffstat of what changed upstream since the last
3644 rebase. False by default.
3645 </p>
3646 </dd>
3648 rebase.autosquash
3649 </dt>
3650 <dd>
3651 <p>
3653 </p>
3654 </dd>
3656 receive.autogc
3657 </dt>
3658 <dd>
3659 <p>
3660 By default, git-receive-pack will run "git-gc --auto" after
3661 receiving data from git-push and updating refs. You can stop
3662 it by setting this variable to false.
3663 </p>
3664 </dd>
3666 receive.fsckObjects
3667 </dt>
3668 <dd>
3669 <p>
3670 If it is set to true, git-receive-pack will check all received
3671 objects. It will abort in the case of a malformed object or a
3672 broken link. The result of an abort are only dangling objects.
3673 Defaults to false.
3674 </p>
3675 </dd>
3677 receive.unpackLimit
3678 </dt>
3679 <dd>
3680 <p>
3681 If the number of objects received in a push is below this
3682 limit then the objects will be unpacked into loose object
3683 files. However if the number of received objects equals or
3684 exceeds this limit then the received pack will be stored as
3685 a pack, after adding any missing delta bases. Storing the
3686 pack from a push can make the push operation complete faster,
3687 especially on slow filesystems. If not set, the value of
3689 </p>
3690 </dd>
3692 receive.denyDeletes
3693 </dt>
3694 <dd>
3695 <p>
3696 If set to true, git-receive-pack will deny a ref update that deletes
3697 the ref. Use this to prevent such a ref deletion via a push.
3698 </p>
3699 </dd>
3701 receive.denyDeleteCurrent
3702 </dt>
3703 <dd>
3704 <p>
3705 If set to true, git-receive-pack will deny a ref update that
3706 deletes the currently checked out branch of a non-bare repository.
3707 </p>
3708 </dd>
3710 receive.denyCurrentBranch
3711 </dt>
3712 <dd>
3713 <p>
3714 If set to true or "refuse", git-receive-pack will deny a ref update
3715 to the currently checked out branch of a non-bare repository.
3716 Such a push is potentially dangerous because it brings the HEAD
3717 out of sync with the index and working tree. If set to "warn",
3718 print a warning of such a push to stderr, but allow the push to
3719 proceed. If set to false or "ignore", allow such pushes with no
3720 message. Defaults to "refuse".
3721 </p>
3722 </dd>
3724 receive.denyNonFastForwards
3725 </dt>
3726 <dd>
3727 <p>
3728 If set to true, git-receive-pack will deny a ref update which is
3729 not a fast-forward. Use this to prevent such an update via a push,
3730 even if that push is forced. This configuration variable is
3731 set when initializing a shared repository.
3732 </p>
3733 </dd>
3735 receive.updateserverinfo
3736 </dt>
3737 <dd>
3738 <p>
3739 If set to true, git-receive-pack will run git-update-server-info
3740 after receiving data from git-push and updating refs.
3741 </p>
3742 </dd>
3745 </dt>
3746 <dd>
3747 <p>
3750 </p>
3751 </dd>
3754 </dt>
3755 <dd>
3756 <p>
3758 </p>
3759 </dd>
3762 </dt>
3763 <dd>
3764 <p>
3765 For remotes that require curl (http, https and ftp), the URL to
3766 the proxy to use for that remote. Set to the empty string to
3767 disable proxying for that remote.
3768 </p>
3769 </dd>
3772 </dt>
3773 <dd>
3774 <p>
3777 </p>
3778 </dd>
3781 </dt>
3782 <dd>
3783 <p>
3786 </p>
3787 </dd>
3790 </dt>
3791 <dd>
3792 <p>
3793 If true, pushing to this remote will automatically behave
3795 </p>
3796 </dd>
3799 </dt>
3800 <dd>
3801 <p>
3802 If true, this remote will be skipped by default when updating
3805 </p>
3806 </dd>
3809 </dt>
3810 <dd>
3811 <p>
3812 If true, this remote will be skipped by default when updating
3815 </p>
3816 </dd>
3819 </dt>
3820 <dd>
3821 <p>
3822 The default program to execute on the remote side when pushing. See
3824 </p>
3825 </dd>
3828 </dt>
3829 <dd>
3830 <p>
3831 The default program to execute on the remote side when fetching. See
3833 </p>
3834 </dd>
3837 </dt>
3838 <dd>
3839 <p>
3840 Setting this value to --no-tags disables automatic tag following when
3844 override this setting. See options --tags and --no-tags of
3846 </p>
3847 </dd>
3850 </dt>
3851 <dd>
3852 <p>
3855 </p>
3856 </dd>
3859 </dt>
3860 <dd>
3861 <p>
3862 The list of remotes which are fetched by "git remote update
3864 </p>
3865 </dd>
3867 repack.usedeltabaseoffset
3868 </dt>
3869 <dd>
3870 <p>
3872 delta-base offset. If you need to share your repository with
3873 git older than version 1.4.4, either directly or via a dumb
3874 protocol such as http, then you need to set this option to
3875 "false" and repack. Access from old git versions over the
3876 native protocol are unaffected by this option.
3877 </p>
3878 </dd>
3880 rerere.autoupdate
3881 </dt>
3882 <dd>
3883 <p>
3885 resulting contents after it cleanly resolves conflicts using
3886 previously recorded resolution. Defaults to false.
3887 </p>
3888 </dd>
3890 rerere.enabled
3891 </dt>
3892 <dd>
3893 <p>
3894 Activate recording of resolved conflicts, so that identical
3895 conflict hunks can be resolved automatically, should they
3899 </p>
3900 </dd>
3902 sendemail.identity
3903 </dt>
3904 <dd>
3905 <p>
3906 A configuration identity. When given, causes values in the
3910 </p>
3911 </dd>
3913 sendemail.smtpencryption
3914 </dt>
3915 <dd>
3916 <p>
3919 </p>
3920 </dd>
3922 sendemail.smtpssl
3923 </dt>
3924 <dd>
3925 <p>
3927 </p>
3928 </dd>
3931 </dt>
3932 <dd>
3933 <p>
3935 found below, taking precedence over those when the this
3936 identity is selected, through command-line or
3938 </p>
3939 </dd>
3941 sendemail.aliasesfile
3942 </dt>
3944 sendemail.aliasfiletype
3945 </dt>
3947 sendemail.bcc
3948 </dt>
3950 sendemail.cc
3951 </dt>
3953 sendemail.cccmd
3954 </dt>
3956 sendemail.chainreplyto
3957 </dt>
3959 sendemail.confirm
3960 </dt>
3962 sendemail.envelopesender
3963 </dt>
3965 sendemail.from
3966 </dt>
3968 sendemail.multiedit
3969 </dt>
3971 sendemail.signedoffbycc
3972 </dt>
3974 sendemail.smtppass
3975 </dt>
3977 sendemail.suppresscc
3978 </dt>
3980 sendemail.suppressfrom
3981 </dt>
3983 sendemail.to
3984 </dt>
3986 sendemail.smtpdomain
3987 </dt>
3989 sendemail.smtpserver
3990 </dt>
3992 sendemail.smtpserverport
3993 </dt>
3995 sendemail.smtpserveroption
3996 </dt>
3998 sendemail.smtpuser
3999 </dt>
4001 sendemail.thread
4002 </dt>
4004 sendemail.validate
4005 </dt>
4006 <dd>
4007 <p>
4009 </p>
4010 </dd>
4012 sendemail.signedoffcc
4013 </dt>
4014 <dd>
4015 <p>
4017 </p>
4018 </dd>
4020 showbranch.default
4021 </dt>
4022 <dd>
4023 <p>
4026 </p>
4027 </dd>
4029 status.relativePaths
4030 </dt>
4031 <dd>
4032 <p>
4035 relative to the repository root (this was the default for git
4036 prior to v1.5.4).
4037 </p>
4038 </dd>
4040 status.showUntrackedFiles
4041 </dt>
4042 <dd>
4043 <p>
4044 By default, <a href="git-status.html">git-status(1)</a> and <a href="git-commit.html">git-commit(1)</a> show
4045 files which are not currently tracked by Git. Directories which
4046 contain only untracked files, are shown with the directory name
4047 only. Showing untracked files means that Git needs to lstat() all
4048 all the files in the whole repository, which might be slow on some
4049 systems. So, this variable controls how the commands displays
4050 the untracked files. Possible values are:
4051 </p>
4053 <li>
4054 <p>
4056 </p>
4057 </li>
4058 <li>
4059 <p>
4061 </p>
4062 </li>
4063 <li>
4064 <p>
4066 </p>
4067 </li>
4068 </ul></div>
4070 This variable can be overridden with the -u|--untracked-files option
4071 of <a href="git-status.html">git-status(1)</a> and <a href="git-commit.html">git-commit(1)</a>.</p></div>
4072 </dd>
4074 status.submodulesummary
4075 </dt>
4076 <dd>
4077 <p>
4078 Defaults to false.
4079 If this is set to a non zero number or true (identical to -1 or an
4080 unlimited number), the submodule summary will be enabled and a
4081 summary of commits for modified submodules will be shown (see
4083 </p>
4084 </dd>
4087 </dt>
4090 </dt>
4093 </dt>
4094 <dd>
4095 <p>
4096 The path within this project, URL, and the updating strategy
4097 for a submodule. These variables are initially populated
4100 <a href="git-submodule.html">git-submodule(1)</a> and <a href="gitmodules.html">gitmodules(5)</a> for details.
4101 </p>
4102 </dd>
4105 </dt>
4106 <dd>
4107 <p>
4108 This option can be used to enable/disable recursive fetching of this
4109 submodule. It can be overridden by using the --[no-]recurse-submodules
4112 file.
4113 </p>
4114 </dd>
4117 </dt>
4118 <dd>
4119 <p>
4120 Defines under what circumstances "git status" and the diff family show
4121 a submodule as modified. When set to "all", it will never be considered
4122 modified, "dirty" will ignore all changes to the submodules work tree and
4123 takes only differences between the HEAD of the submodule and the commit
4124 recorded in the superproject into account. "untracked" will additionally
4125 let submodules with modified tracked files in their work tree show up.
4126 Using "none" (the default when this option is not set) also shows
4127 submodules that have untracked files in their work tree as changed.
4128 This setting overrides any setting made in .gitmodules for this submodule,
4129 both settings can be overridden on the command line by using the
4130 "--ignore-submodules" option.
4131 </p>
4132 </dd>
4134 tar.umask
4135 </dt>
4136 <dd>
4137 <p>
4138 This variable can be used to restrict the permission bits of
4139 tar archive entries. The default is 0002, which turns off the
4140 world write bit. The special value "user" indicates that the
4143 </p>
4144 </dd>
4146 transfer.unpackLimit
4147 </dt>
4148 <dd>
4149 <p>
4151 not set, the value of this variable is used instead.
4152 The default value is 100.
4153 </p>
4154 </dd>
4157 </dt>
4158 <dd>
4159 <p>
4160 Any URL that starts with this value will be rewritten to
4162 large number of repositories, and serves them with multiple
4163 access methods, and some users need to use different access
4164 methods, this feature allows people to specify any of the
4165 equivalent URLs and have git automatically rewrite the URL to
4166 the best alternative for the particular user, even for a
4167 never-before-seen repository on the site. When more than one
4168 insteadOf strings match a given URL, the longest match is used.
4169 </p>
4170 </dd>
4173 </dt>
4174 <dd>
4175 <p>
4176 Any URL that starts with this value will not be pushed to;
4178 resulting URL will be pushed to. In cases where some site serves
4179 a large number of repositories, and serves them with multiple
4180 access methods, some of which do not allow push, this feature
4181 allows people to specify a pull-only URL and have git
4182 automatically use an appropriate URL to push, even for a
4183 never-before-seen repository on the site. When more than one
4184 pushInsteadOf strings match a given URL, the longest match is
4185 used. If a remote has an explicit pushurl, git will ignore this
4186 setting for that remote.
4187 </p>
4188 </dd>
4190 user.email
4191 </dt>
4192 <dd>
4193 <p>
4194 Your email address to be recorded in any newly created commits.
4196 <em>EMAIL</em> environment variables. See <a href="git-commit-tree.html">git-commit-tree(1)</a>.
4197 </p>
4198 </dd>
4200 user.name
4201 </dt>
4202 <dd>
4203 <p>
4204 Your full name to be recorded in any newly created commits.
4207 </p>
4208 </dd>
4210 user.signingkey
4211 </dt>
4212 <dd>
4213 <p>
4215 automatically when creating a signed tag, you can override the
4216 default selection with this variable. This option is passed
4217 unchanged to gpg’s --local-user parameter, so you may specify a key
4218 using any method that gpg supports.
4219 </p>
4220 </dd>
4222 web.browser
4223 </dt>
4224 <dd>
4225 <p>
4226 Specify a web browser that may be used by some commands.
4227 Currently only <a href="git-instaweb.html">git-instaweb(1)</a> and <a href="git-help.html">git-help(1)</a>
4228 may use it.
4229 </p>
4230 </dd>
4231 </dl></div>
4232 </div>
4236 </div>
4240 </div>
4241 </div>
4242 </body>
4243 </html>